Running MongoDB on Google Compute Engine
Tuesday, June 24, 2014
With over a dozen different virtual machine types, and the great price for performance of persistent disks, we think Google Compute Engine is a great place for running MongoDB. We are excited to be working with MongoDB to bring together documentation, resources, and partners to help you get up and running, to build, and to scale your application.
For self-managed production deployments, you have a range of software management options, such as Puppet, Chef, Salt, and Ansible. For fully-managed deployments, you can work with partners such as MongoLab.
But when you are just getting a project started, you want to get a proving ground up and running quickly. You'd also like to to find the documentation you need from one place. You'll be able to find resources you need to deploy MongoDB on Compute Engine at http://cloud.google.com/solutions/mongodb.
With Click to Deploy MongoDB available in the Developer Console, you'll be able to bring up a Compute Engine cluster running MongoDB in a few minutes. Through the web interface, you can choose how many MongoDB server and arbiter nodes, their associated virtual machine types, and the size of your data disk volumes.
We'll continue to add features to the Click to Deploy infrastructure and look to implement best practices for MongoDB on Google Compute Engine. Here's one key tip you can find in the MongoDB on Google Compute Engine solutions paper:
Check it all out at http://cloud.google.com/solutions/mongodb.
-Posted by Matt Bookman, Solutions Architect
MongoDB, is registered trademarks of MongoDB, Inc. All other trademarks cited here are the property of their respective owners.
For self-managed production deployments, you have a range of software management options, such as Puppet, Chef, Salt, and Ansible. For fully-managed deployments, you can work with partners such as MongoLab.
But when you are just getting a project started, you want to get a proving ground up and running quickly. You'd also like to to find the documentation you need from one place. You'll be able to find resources you need to deploy MongoDB on Compute Engine at http://cloud.google.com/solutions/mongodb.
With Click to Deploy MongoDB available in the Developer Console, you'll be able to bring up a Compute Engine cluster running MongoDB in a few minutes. Through the web interface, you can choose how many MongoDB server and arbiter nodes, their associated virtual machine types, and the size of your data disk volumes.
We'll continue to add features to the Click to Deploy infrastructure and look to implement best practices for MongoDB on Google Compute Engine. Here's one key tip you can find in the MongoDB on Google Compute Engine solutions paper:
Put your MongoDB journal files and data files on the same disk
It is a common recommendation to separate components onto different storage devices. However, persistent disk already stripes data across a very large number of volumes, so there is no need to do it yourself.
MongoDB journal data is small and putting it on its own disk means either creating a small disk with insufficient performance or creating a large disk that goes mostly unused. Put your MongoDB journal files on the same disk as your data. Otherwise putting your MongoDB journal files on a small persistent disk will dramatically decrease performance of database writes.
Check it all out at http://cloud.google.com/solutions/mongodb.
-Posted by Matt Bookman, Solutions Architect
MongoDB, is registered trademarks of MongoDB, Inc. All other trademarks cited here are the property of their respective owners.