Deploying MongoDB on Azure - Eduard Koller (Microsoft), David Makogon (Microsoft), Sridhar Nanjundeswaran (10gen)

MongoSV 2011

A brief overview of building and deploying applications using MongoDB Replica Sets on Windows Azure followed by an interactive session to discuss recommended configurations and tips (and tricks).

Transcript

1. Deploying MongoDB on Azure Eduard Koller, Microsoft Sridhar Nanjundeswaran, 10gen David Makogon, Microsoft
2. Windows Azure Platform •  Microso'’s  cloud  pla/orm  to  build,  host  and  scale   applica7ons   •  Internet-­‐scale  compu7ng  and  services   •  Hosted  in  Microso'  data  centers   Compute   Storage   Management   CDN  
3. Why Windows Azure? •  More time coding, less time managing hardware and/or deploying applications •  Scale your applications up or out on demand •  Trust: Enterprise class service backed by reliable SLAs •  Efficiency: Microsoft operates the Windows Azure platform at internet-scale
4. Azure Interoperability •  Data portability •  Cloud Standards •  Ease of Migration and Deployment •  Developer choice
5. Why MongoDB on Azure? •  High availability built in •  Data replication and durability built in •  You can scale up on demand your application and the MongoDB database •  You can scale out on demand your application and the MongoDB database(1)
6. MongoDB on Windows Azure Sample deployment:
7. VM high-availability
8. Data durability
9. DR and geo-replication
10. Scale up & down, in-place upgrade
11. API-driven management
12. MongoDB on Azure implementation history •  Manual setup of replica sets – demo’ed at MongoSV 2010. David Makogon •  Single instance with standby – demo’ed at MongoSF 2011. Sridhar Nanjundeswaran •  Replica set support - now
13. Highlights •  Uses standard MongoDB binaries •  Code is open sourced •  Works with VS Express •  Automatic replica set initiation on deploy •  Survives reboots of instances •  Integration with Azure diagnostics •  Data persisted on blob storage
14. DEMO MongoDB on Azure
15. Challenges •  Debugging when building –  On emulator debug –  On deployment, trace + tools such as Cerebrata   •  IP potentially changes on reboot –  DNS within mongodb. New cloud command •  Bandwidth –  Requires at least medium instance –  Don’t store mongod.log on blob storage •  Testing IP change –  Reduce instance count and increase
16. The Solution •  Source – https://github.com/mongodb/mongo-azure •  Documentation – http://www.mongodb.org/display/DOCS/ MongoDB+on+Azure •  Issues – mongodb-user google group – #mongodb IRC – https://jira.mongodb.org/browse/AZURE
17. The Future •  Scale out using replica sets •  MongoDB Monitoring •  Backup and Recovery •  Sharding