Here’s what we’re reading this week at MongoDB:
ComputerWorld: The Weather Channel forecasts heavy NoSQL ahead
Crain’s: 2014 Fast 50
Diginomica: Open source or bust – developer engagement, MongoDB style
Eliot’s Ramblings: The Road to MMS Automation
eWeek: MongoDB Management Service Tweaked for Flexibility
GigaOm: MongoDB targets ‘massive’ revenue stream with new cloud-based management service
MongoDB Community Blog: MongoDB Management Service Re-imagined: The Easiest Way to Run MongoDB
MongoDB Corporate Blog: Too Many Projects, Too Little Time: Deliver MongoDB-as-a-Service
Too Many Projects, Too Little Time: Deliver MongoDB-as-a-Service
What do a leading investment bank, a PaaS for mobile app developers and one of the largest US government departments all have in common? Each one needed to power a new wave of applications with a single database. Of course it didn’t make sense for each database instance to run on its own infrastructure. So they decided to build a shared service to standardize the way multiple applications and project teams consumed the database. That database was MongoDB. And what they built was MongoDB-as-a-Service. These organizations are not alone. MongoDB is the fastest growing database community on the planet . As more companies move from initial pilots to full scale production, IT groups are challenged to bring order to chaos. They need to maintain consistent operational best practices and enforce corporate governance mandates and BU accountability across multiple projects. This is where delivering MongoDB-as-a-Service comes in. One pool of shared resources – running in a private data center or in a public cloud – serving multiple tenants, each with unique workload requirements. Building something like this from scratch isn’t easy. But you don’t have to reinvent the wheel either. We’ve assembled best practices from multiple “as-a-service” projects to create the top 10 considerations to delivering MongoDB-as-a-Service . So what are the top 10 things to think about? You should download the whitepaper, but as a summary: Step 1: Identify Common Workload Requirements Presents checklists you can use to capture both current and future database loads and technology specs. This provides input to the infrastructure you need to provision. Step 2: Hardware & OS Selection Identifies the general-purpose building blocks you should use to power the service. Step 3: Virtualization Strategy Helps guide you to the virtualization technology that will get the most out of your hardware. Step 4: Enabling Multi-Tenant Services What do you need – maximum density of tenants per server, or maximum isolation between tenants? It doesn’t have to be either/or. You can blend multiple approaches to meet the demands of multiple apps. Step 5: Enforcing Security Isolation between Tenants Guidance on how to maintain strict isolation between each project, with full account and auditing control. Step 6: Meeting Service Level Agreement (SLA) Requirements How can you be sure you can deliver continuous availability to your customers? How can you scale those apps that need it, when they need it? This section shows you how. Step 7: Managing the MongoDB Service You need to provision new services fast. You need proactive monitoring to identify potential issues before an outage brings all your apps down. You need to ensure each teams’ data is safe and can recover from disasters. We present the management platform you need to accomplish all of these things. Step 8: Cost Accounting & Chargeback There is no such thing as a free ride….you deliver value for money, so now its time to make sure the project teams pay for what they consume. Step 9: Define the Implementation Plan Where to start? You need the right people on board. This section helps you track down the (willing?) volunteers Step 10: Production-Grade DBaaS You need your MongoDB instances to be certified, secure and supported. We have just the thing. If the above has piqued your interest, fill in a few details and download our new whitepaper now: MongoDB-as-a-Service: Top 10 Considerations .
A Hub for Eco-Positivity
In this guest blog post, Natalia Goncharova, founder and web developer for EcoHub — an online platform where people can search for and connect with more than 13,000 companies, NGOs, and governmental agencies across 200-plus countries — describes how the company uses MongoDB to generate momentum around global environmental change. There is no denying that sustainability has become a global concern. In fact, the topic has gone mainstream. A 2021 report by the Economist Intelligence Unit (EIU) shows a 71% rise in the popularity of searches for sustainable goods over the past five years. The report “measures engagement, awareness and action for nature in 27 languages, across 54 countries, covering 80% of the world’s population.” The EIU report states that the sustainability trend is accelerating in developing and emerging countries including Ecuador and Indonesia. For me, it’s not a lack of positive sentiment that is holding back change; it is our ability to turn ideas and goodwill into action. We need a way of harnessing this collective sentiment. In 2020, the decision to found EcoHub and devote so much time to it was a difficult one to make. I had just been promoted to team leader at work, and things were going well. Leaving my job with the goal of helping to protect our environment sounded ridiculous at times. Many questions raced through my mind, the most insistent one being: Will I be able to actually make a difference? However, as you’ll see in this post, my decision was ultimately quite clear. What is EcoHub? When I created EcoHub, my principal aim was to connect ecological NGOs and businesses. Now, EcoHub enables users to search a database of more than 10,000 organizations in more than 200 countries. You can search via a map or keyword. By making it easier to connect, EcoHub lets users quickly build networks of sustainably minded organizations. We believe networks are key to spreading good ideas, stripping out duplication, and building expertise. Building the platform has been a monumental task. I have developed it myself over the past few months, acting as product manager, project manager, and full-stack developer. (It wouldn’t be possible without my research, design, and media teams as well.) During the development of the EcoHub platform on MongoDB, the flexible schema helped us edit and add new fields in a document because the process doesn’t require defining data types. We had a situation in which it was necessary to change the schema and implement changes for all documents in the database. In this case, modifying the entire collection with MongoDB didn’t take long for an experienced developer. Additionally, MongoDB’s document-oriented data model works well with the way developers think. The model reflects how we see the objects in the codebase and makes the process easier. In my experience, the best resource to find answers when I ran into a question or issue was MongoDB documentation . It provides a good explanation of almost anything you want to do in your database. Search is everything In technical terms, my choices were ReactJS, NodeJS, and MongoDB. It is the latter that is so important to the effectiveness of the EcoHub platform. Search is everything. The easier we can make it for individuals or organizations to find like minds, the better. I knew from the start that I’d need a cloud-based database with strong querying abilities. As an experienced developer, I had previous experience with MongoDB and knew the company to be reliable, with excellent documentation and a really strong community of developers. It was a clear choice from the start. Choosing our partners carefully is also important. If EcoHub is to build awareness of environmental issues and foster collaboration, then we must ensure we make intelligent choices in terms of the companies we work with. I have been impressed with MongoDB’s sustainability commitments , particularly around diversity and inclusion, carbon reduction, and its appetite for exploring the way the business has an impact globally and locally. EcoHub search is built on the community version of MongoDB , which enables us to work quickly, implement easily and deliver the right performance. Importantly, as EcoHub grows and develops, MongoDB also allows us to make changes on the fly. As environmental concerns continue to grow, our database will expand. MongoDB enables our users to search, discover, and connect with environmental organizations all over the world. I believe these connections are key to sharing knowledge and expertise and helping local citizens coordinate their sustainability efforts. Commitment to sustainability When it came down to it, the decision to build EcoHub wasn’t as difficult as I initially thought. My commitment to sustainability actually started when I was young: I can remember myself at 8 years old, glued to the window, waiting for the monthly Greenpeace magazine to arrive. Later, that commitment grew as I went to university and graduated with a degree in Environmental Protection and Engineering. Soon after, I founded my first ecology organization and rallied our cityagainst businesses wanting to cut down our beautiful city parks. Starting EcoHub was a natural and exciting next step, despite the risks and unknown factors. I hope we can all join hands to create a sustainable future for ourselves, our children, and our animals and plants, and keep our planet beautiful and healthy. MongoDB Atlas makes operating MongoDB a snap at any scale. Determine the costs and benefits with our cost calculator .