Growing MongoDB on AWS
- 1. Growing MongoDB on AWS Colin Howe @colinhowe
- 2. Who am I? I run engineering at Conversocial. We help companies do social customer service. http://www.conversocial.com Love coding, ultimate frisbee and pudding
- 3. Growing MongoDB on AWS Tips for ensuring you can grow MongoDB on AWS as your business needs grow. Mandatory meaningless graph
- 4. Single Server - Ephemeral Single server with instance storage. Not really advised. Must haves: ● Journalling http://www.mongodb.org/display/DOCS/Journaling ● Regular backups http://www.mongodb.org/display/DOCS/Backups
- 5. Single Server - Ephemeral Pros: Easy to configure. Cheap. Cons: No redundancy. Data since last backup is lost on server death.
- 6. Single Server - EBS Same as the last but move storage over to EBS. EBS is slow. RAID 10 it. http://bit.ly/mongodb-raid10
- 7. Single Server - EBS Pros: Easy to configure. Data should still be available on server death. Cheapish. Cons: No redundancy.
- 8. Single Server - No redundancy
- 9. Enter Replication Primary server replicates to secondary servers Use multiple Availability Zones (AZs).
- 10. Two servers, one arbiter Cheapest replica set configuration. Arbiter ensures an odd number of votes. The arbiter can be a micro instance.
- 11. Two servers, one arbiter Pros: Cheapish. Some failover. Cons: Only one failover. What if you fail again?
- 12. Three servers Standard replica set configuration.
- 13. Three servers Pros: Lots of redundancy. High read capacity when one server fails. Cons: Starts to get pricey.
- 14. Where next? Horizontal and vertical scaling.
- 15. Vertical scaling Use EBS boot. Turn the server off. Resize. Turn it back on. Seconds of downtime when using a replica set. Without replica sets you will have downtime
- 16. Vertical scaling - SSDs If you can afford them SSDs are the King. ● Conversocial got 43% faster. ● 90% iowait went to ~3% user, 0% iowait. All numbers compared to instance with largest memory (68.4gb)
- 17. Horizontal read scaling Add more secondaries and use slave queries. Really easy. Make sure you have a hidden backup server. Backups kill read performance. Use write concerns for consistent reads.
- 18. Horizontal write scaling - Sharding Fairly easy with MongoDB. Backups get harder. More to manage and configure. Automate it.
- 19. When to Shard? If you know your data structure then sooner If you don't... later Changing shard keys is not trivial
- 20. Enterprise Availability If you're hunting for the final decimal places of availability... You're probably going to break your application more frequently than Amazon has a whole region outage. But...
- 21. Enterprise Availability Multiple regions are the next step. Harder as you go outside the firewall. VPNs or SSH tunnels are your friend here.
- 22. Tools to Help You MMS - Mongo's Monitoring System (FREE) Chef/Puppet - automate as much as you can #mongodb and MongoDB user group 10gen
- 23. Thanks for Listening! Any questions? Feeling shy? You can always reach me on Twitter @colinhowe Slides will be put online