In this recipe, we will be evaluating one of the vendors, MongoLab, providing MongoDB as a service. This introductory recipe will introduce to you what MongoDB as a service is, and then it will demonstrate how to set up and manage an account in MongoLab (https://mongolab.com/).
In all the recipes in this book, we have covered setting up, administering, monitoring, and developing the instances of MongoDB in the organizations/personal premises so far. This not only needs man power with the appropriate skill set to manage the deployments, but also appropriate hardware to install and run Mongo servers. This needs large investments upfront that might not be a viable solution for start-ups or even organizations that are not clear about adopting this technology or migrating to it. They might want to evaluate it and see how it goes before moving full fledged to this solution. What would be ideal is to have a service provider that takes care of hosting the MongoDB deployments, managing, and monitoring the deployments, and providing support. The organizations that opt for these services need not invest upfront in setting up the servers nor recruit or outsource to consultants for the administration and monitoring of the instances. All that one needs to do is choose the hardware and software platform, configuration, and the appropriate MongoDB version, and set up an environment from a user-friendly GUI. It even gives you an option to use your existing cloud provider's servers.
Having explained in brief what these vendor-hosting services do and why they are needed, we will start this recipe by setting up an account with MongoLab and see some basic user and account management. MongoLab is by no means the only hosting provider for MongoDB. You might also want to take a look at http://www.mongohq.com/ and http://www.objectrocket.com/. At the time of writing this book, MongoDB itself started providing MongoDB as a service on Azure cloud and is currently in beta phase.
There is nothing much to explain in this section. The setup process and user administration are pretty simple. Note that the users we added here are not database users. These are the users that have access to Account on MongoLab, for which we added them. The account can be the name of the organization and can be seen at the top of the screen. The multifactor authentication account set up in the Google Authenticator software on the handheld device should not be deleted, as whenever the user logs in to the MongoLab account from the browser, he will be asked to enter the Google Authenticator account to continue.