Building the future of Digital Television and Enterprise Database Management with MongoDB at Swisscom
•
0 likes•1,236 views
Presented by Lukas Lehmann, Streamlead Apps & Services Application Cloud and Markus Zehnder, IPTV Engineer, Swisscom Switzerland’s leading telecom provider, Swisscom, uses MongoDB in a number of areas. This presentation will dive into two particular applications at Swisscom: the database-as-a-service offering on their PaaS Platform and Swisscom TV 2.0, an award-winning Multiscreen IP TV service. Lukas and Markus will walk through why they chose to use MongoDB for these projects and will address how MongoDB reduced latency and helped them scale. The team will also address how they were able to leverage MongoDB’s Ops Manager API to build their Enterprise database-as-a-service that is used that is widely used internally, by start ups as well as by some of the largest enterprises.
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (6)
Similar to Building the future of Digital Television and Enterprise Database Management with MongoDB at Swisscom
Similar to Building the future of Digital Television and Enterprise Database Management with MongoDB at Swisscom (20)
More from MongoDB
More from MongoDB (20)
Recently uploaded
Recently uploaded (20)
Building the future of Digital Television and Enterprise Database Management with MongoDB at Swisscom
- 1. Swisscom Cloud Offerings – mongoDB as a Service Lukas Lehmann MongoDB Days Germany Munich, October 2015
- 2. Agenda • Managed Service Status Quo • Swisscom ApplicationCloud • Version 1.0 mainly VM based • Version 2.0 container based • Feature Requests • Case study IP TV ©Swisscom
- 3. Managed desires vs product based offering Heterogeneous environment Homogenous environment Different Desirable Different Different One Predefined One One OS Sizes Hardware profiles Storage backend ©Swisscom
- 6. Big Picture Create Service Process I 6 AppCloud User Services Network Cloud Foundry Network Portal or CLI Cloud Foundry cf create service ent-mongodb ©Swisscom
- 7. Big Picture Create Service Process II 7 AppCloud User Services Network Cloud Foundry Network Portal or CLI Cloud Foundry Service Manager cf create service ent-mongodb ©Swisscom
- 8. Big Picture Create Service Process III 8 AppCloud User Services Network Cloud Foundry Network Portal or CLI Cloud Foundry Service Manager Management Node 1 MMS HTTP ServiceChange config cf create service ent-mongodb ©Swisscom
- 9. Big Picture Create Service Process IV 9 AppCloud User Services Network Cloud Foundry Network Portal or CLI Cloud Foundry Service Manager Management Node 1 MMS HTTP Service Data Volume MongoDB Node MMS Automation Agent Change config Get config MongoDB 1 cf create service ent-mongodb - One MongoDB perVM spawn up by automation agent ©Swisscom
- 10. Detail View MongoDB Management 10 AppCloud User Services Network Cloud Foundry Network Portal or CLI Cloud Foundry Service Manager Management Node 1 MMS HTTP Service Data Volume MongoDB Node MMS Automation Agent Change config Get config MongoDB 1 cf create service ent-mongodb OpsManager setup Data Volume Management Node 1 MMS HTTP Service MMS DB Primary Management Node 2 MMS DB Sec. Management Node 3 MMS DB Sec. Monitoring Agent MongoDB Node MMS Automation Agent ©Swisscom
- 11. Access MongoDB from Cloud Foundry 11 AppCloud User Services Network Cloud Foundry Network Portal or CLI Cloud Controller Service Manager Management Node 1 MMS HTTP Service Data Volume MongoDB Node MMS Automation Agent MongoDB 1 cf create service ent-mongodb DEA App (Container) App connects directly to service Data Volume MongoDB Node MMS Automation Agent MongoDB 2 ©Swisscom
- 12. Service Broker function create service mongodb 12 AppCloud User Cloud Foundry Network Portal or CLI Cloud Foundry Service Manager Management Node 1 MMS HTTP Service Data Volume MongoDB Node MMS Automation Agent Change config Get config MongoDB 1 cf create service ent-mongodb - One MongoDB perVM spawn up by automation agent Detail view creation Creates new standalone MongoDB on a free node incurrent mms group config Portal or CLI Cloud Controller Service Broker MMS HTTP Service MongoD Create Service(HTTP) Create Service(HTTP) ©Swisscom
- 13. Service Broker function create service mongodb 13 AppCloud User Cloud Foundry Network Portal or CLI Cloud Foundry Service Manager Management Node 1 MMS HTTP Service Data Volume MongoDB Node MMS Automation Agent Change config Get config MongoDB 1 cf create service ent-mongodb - One MongoDB perVM spawn up by automation agent Detail view binding Creates a new user in db with native mongodb command Portal or CLI Cloud Controller Service Broker MMS HTTP Service MongoD Create Service(HTTP) Create Service(HTTP) Bind service (HTTP) Bind service (HTTP) ©Swisscom
- 14. Backup functionality 18.10.15 14 Services Network Service Manager Management Node 1 MMS HTTP Service Data Volume MongoDB Node MongoDB Trigger backup execution New snapshot OpsManager 2.0 preview Management Node 2 Backup Deamon Take snapshot (sync Opslog ) Automation Agent Sync data to external S3Storage ©Swisscom
- 15. Restore functionality 15 Services Network Service Manager Management Node 1 MMS HTTP Service Trigger restoreexecution Restore snapshot OpsManager 2.0 preview Management Node 2 Backup Deamon Download and restore snapshot Data Volume MongoDB Node MongoDB Automation Agent Sync data from external S3Storage ©Swisscom
- 17. Automation Agent in Docker Container 17 AppCloud User Services Network Cloud Foundry Network Portal or CLI Cloud Foundry Service Manager Management Node 1 MMS HTTP Service Vol. Service. 1 Flocker node Create new Container /w automation agent Update config Flocker API Agent Docker Automation Agent (service container) Vol. Service 4 Vol. Service 3 Vol. Service 2 Vol. Service 1 Attach volume to VM (container) Get config Container preview Automationagent in Container cf create service ent-mongodb ©Swisscom
- 18. Why Containers? • Less overhead • More efficiency • More flexibility • Move towards generic solution ©Swisscom
- 19. Custom Feature Request • Swisscom and others? as Customer need the following features to implement the solution: – Ops Manager Backup/Restore function viaAPI like described in slides above – Official support from MongoDB for containers i.e. Docker – Less hostname dependency – Supporting ability forservice discovery ©Swisscom
- 20. Mongo DB on Swisscom TV 2.0 Markus Zehnder Mongo DB Days Germany Munich, October 2015
- 21. Agenda • What is Swisscom TV 2.0 • Requirements • Why we chose Mongo DB • Architecture • QA ©Swisscom
- 22. Swisscom TV 2.0 in brief • Over 250 channels, including 100 HD channels • Replay available for 7 days on over 250 channels • Record as many programms as youlike, even those Shown in the past • Video Store with subscriptionoption • Over 800k Customers described • “Best Multiscreen TV Service” in 2015 ©Swisscom
- 23. Swisscom TV 2.0 in the cloud Access your recordings from any device whenever you like and wherever you are Secure data in Switzerland Open and flexible platform Cloud recording Record as many programmes as you like simultaneously Environmentally-‐friendly box with a longer service life ©Swisscom
- 24. Requirements • EPG, VOD, Radio, etc. metadata need to be stored • Pictures are needed as well in the DB • Metadata size > 10GB, Pictures size > 20GB • Data is generally static, but can change several times a day • Amount of devices which will access the data > 1Mio. • DB needs to be highly available ©Swisscom
- 25. Why we chose Mongo DB • Data is unstructured, so hard to store it in a relational DB • It is easy to transform the XML Data(Source) into JSON-Format • Mongo DB is extremly fast in reading data • Open Source • Easy to scale horizontally ©Swisscom
- 26. ©Swisscom
- 27. Summary • Technical View – Data flexibility – Easy to scale horizontally – Error resilient clusterfunctionality • Get used to MongoDB – Easy2go installationdocs – Great pre-sales/consulting team ©Swisscom
- 28. Q & A ©Swisscom