MongoDB Deployment Strategies

PROBLEM:
Ready to deploy MongoDB? Here's what you need to know

SOLUTION:

Use Replication
Replication is the best way to ensure the safety of your data. It is recommended that you use replica sets, a form of asynchronous master/slave replication that adds automatic failover and automatic recovery of member nodes.
More information on replication:
• Replica Sets
• Best practices for replica sets on EC2

Sharding is there when you need it
If your data exceeds the resources of a single database server, MongoDB can convert to a sharded cluster for horizontal scaling across multiple nodes. With MongoDB sharding, the failover and balancing of nodes is handled automatically, with few or no changes to the original application code.

Deploying in the cloud
MongoDB was designed to run on commodity and virtualized environments. Because it does not depend on high end compute, network or storage resources, your deployment is not limited by the biggest server resources you can get in cloud environments like Amazon EC2 or Rackspace Cloud. You can add additional storage, memory and transaction capacity by adding more virtual servers to your deployment.
• Docs: Amazon EC2
• Docs: VMware Cloud Foundry
• Docs: Red Hat OpenShift
• Docs: Windows Azure
• Docs: Hosting Center

Monitoring your deployment
MongoDB includes many diagnostic commands and tools, like mongostat, the query profiler, and more. In addition the open source community has built plugins from monitoring tools like Ganglia, munin, and cacti.
In addition, 10gen offers a cloud-based monitoring and alerting solution for MongoDB deployments called MongoDB Monitoring Service (MMS). MMS is a publicly available software-as-a-service solution available at mms.10gen.com.

If you find this solution useful, you are welcome to press one of the ads in this page.. Thanks!