Alex Williams for TechCrunch:

MongoHQ has raised $6 million from Trinity Ventures and a host of investors for its database service for developers. The company will use the funds to expand its public cloud offering and improve its management tools for MongoDB, the popular NoSQL database.

Undeniably there’s a lot of demand for MongoDB. 10gen is also growing fast.

But how safe is to build a business around a product that is not in your control?

Original title and link: MongoHQ Raises More Funding for MongoDB as Service Engine (NoSQL database©myNoSQL)

via: http://techcrunch.com/2012/10/18/mongohq-raises-6-million-for-database-as-service-engine/

Leaving aside for a second the aspect of immediate win for 10gen and quite possibly the visible benefits for the end users, I’m wondering if such partnerships (or the lack of them) could be part of the answer to the question why only some NoSQL databases are present in managed hosting offers.

Here’s how MongoLab is introducing this partnership:

MongoLab provides, as always, primary support for operational issues (e.g. password resets, service plan upgrades, maintenance and monitoring) and usage guidance (e.g. index recommendations, schema design).  Starting now, 10gen provides support escalation for code-level database and driver issues, acting as our backstop to provide patches or effective workarounds to issues that can not be solved by configuration or architecture changes.

From my NoSQL market observer position, it looks like a win-win-win situation.

Original title and link: 10gen Signs Partnerships to Strengthen MongoDB Hosting (NoSQL database©myNoSQL)

via: http://blog.10gen.com/post/18067595934/three-new-cloud-providers-join-the-mongodb-ecosystem

MongoHQ, a MongoDB hosting solution:

Now, we are excited to announce that we offer high-availability multi-node replica set plans on our MongoHQ platform. We are pretty excited about this release, as it makes available some great features that our users have been asking for, including:

• High availability databases with automatic failover
• Nodes located in multiple availability zones
• Dedicated volumes to maximize read/write performance
• Slave nodes that can be used as read-slaves for enhanced read throughput

If scaling MongoDB with replica sets and auto-sharing is so easy, I’m wondering why it took MongoHQ so long to add support only for replica sets.

Original title and link: MongoHQ Announces MongoDB Replica Set Support (NoSQL databases © myNoSQL)

via: http://blog.mongohq.com/post/6136673911/announcing-mongohq-replica-set-plans