DevOps: All content tagged as DevOps in NoSQL databases and polyglot persistence
Pierre Bailet and Mathieu Poumeyrol of fotopedia (a French photo site) share their experience of operating a small MongoDB cluster since Sep.2009 compared to a MySQL cluster.
Some details about fotopedia:
- fotopedia is 100% on AWS
- Amazon RDS for MySQL
- 4 nodes MongoDB cluster
- 150mil. photo views
- no alter table
- background index creation
- data backup & restoration
- note: as far as I can tell MySQL is able to do the same
- replica sets
- hardware migration
- note: the same procedure can be used for MySQL
Before leaving you with the slides, here is an interesting accepted trade-off:
Quietly losing seconds of writes is preferable to:
- weekly minutes-long maintenance periods
- minutes-long unscheduled downtime and manual failover in case of hardware failures
Great slides from mongolab‘s Todd O. Dampier about operating MongoDB:
- Stay up => high availability
- Stay fast => performance & scale
- Take good care of your data => data durability
- Always know what’s going on => monitoring & alerting
Whatever database you are planning to use for a busy application, someone that specialized in operating it will give you the best insights. They’ve seen the best and worst of it.
The guys from Boxed Ice have already published a lot about their experience running MongoDB in production, plus a series of posts advising on MongoDB monitoring. Actually they are offering a hosted service for MongoDB monitoring: Server Density .
If you still don’t have MongoDB monitoring in place—unfortunately Foursquare had to learn what this means the hard way—check this talk from David Mytton.
The video quality is very low and I couldn’t embed it here. ↩
Original title and link: Monitoring MongoDB ( ©myNoSQL)