Atlas: Our journey from a Python monolith to a managed platform
Mar 4, 2021Naphat Sanguansin

Summary
This post details the journey from a monolithic Python server (Metaserver) to a managed platform called Atlas. Atlas aims to provide the benefits of a Service Oriented Architecture (SOA) with minimized operational costs for self-contained functionalities. It abstracts away infrastructure management for developers, allowing them to focus on writing endpoint logic. The migration involved standardizing on gRPC and Envoy, and introducing autoscaling and canary analysis. The post contrasts the developer experience before and after Atlas, highlighting improvements in code structure, independent and consistent pushes, and reduced infrastructure debt. Atlas coexists with larger, independently operated services.
More from the Internal Load Balancing Service trail
- What’s new with Robinhood, our in-house load balancing service
- How we migrated Dropbox from Nginx to Envoy
- Enhancing Bandaid load balancing at Dropbox by leveraging real-time backend server load information
- Meet Bandaid, the Dropbox service proxy
- Optimizing web servers for high throughput and low latency