Valiton / Hubert Burda Media shares insights about the challenges they faced with self-hosted MongoDB clusters on AWS and how they solved it with the migration to MongoDB Atlas
Moving from AWS to Atlas - Our Motivation and Journey from Self-Hosted to Managed MongoDB
1. Copyright Valiton GmbH 1
Moving from AWS to
Atlas
Our Motivation and Journey from
Self-Hosted to Managed MongoDB
26th
June 2019
2. Copyright Valiton GmbH 2
Personal Background
2011
2009
Web Developer at food IT Consulting
2013
Co-Founder of allergenis UG
2016
now
Freelancer
Software-Engineer at Valiton GmbH
Christoph Caprano
Christoph.Caprano@valiton.com
23. Copyright Valiton GmbH 23
Performance Boost via Performance Advisor
The number of database objects
requested for a query has been
drastically reduced.
This has caused the API to respond
twice as fast on average (~15 ms instead
of ~30 ms).
This reduces the average query
execution time from up to 7 ms to
significantly less than 1 ms.
Query Targeting Query Executor AVG API Response Time
24. Copyright Valiton GmbH 24
Look back: Challenges with Self-Hosted Architecture
Security Monitoring Maintenance
Authentication
IP Whitelisting
In parallel AWS and Atlas Version Upgrade: SaaS
Scaling: SaaS
25. Copyright Valiton GmbH 25
How to merge AWS and Atlas logs?
Problem: No Grafana integration yet available
26. Copyright Valiton GmbH 26
Solution: Develop and Open-Source Atlas Grafana
Plugin
Get the plugin:
https://github.com/valiton/grafana-mongodb-atlas-datasource
29. Copyright Valiton GmbH 29
What‘s next?
● Participation at MongoDB University
● Use Functions added in MongoDB > 3.0
● Data and Service Redesign
https://www.mongodb.com/blog/post/building-with-patterns-a-summary
● Implementation of Aggregation Pipelines
30. Copyright Valiton GmbH 30
Q & A
Security Monitoring Maintenance
Authentication
IP Whitelisting
In parallel AWS and Atlas Version Upgrade: SaaS
Scaling: SaaS