Otherwise, technical debt and code complexity compound very quickly. The single most important takeaway from this multi-year effort is that well-thought-out code composition, early in a project's lifetime, is essential. The authors draw a key conclusion regarding the migration process: Currently, Atlas is serving more than 25% of the monolith traffic it aims to replace. Building Atlas is a multi-year journey, still taking place today. The reason for building Atlas was to replace Dropbox's central Python monolith called Metaserver. However, to de-risk their migration and ensure low engineering costs, they decided to continue hosting services on the same deployment orchestration platform used by the rest of Dropbox. According to the authors, Naphat Sanguansin and Utsav Shah, they evaluated using off-the-shelf solutions to run the platform. Atlas provides its users with an experience of serverless systems such as AWS Fargate while being backed by automatically provisioned services behind the scenes. In a recent blog post, Dropbox revealed Atlas, a platform whose aim is to provide various benefits of a Service Oriented Architecture while minimizing the operational cost of owning a service.Ītlas' goal is to support small, self-contained functionality, saving product teams the overhead of managing a full-blown service, including capacity planning, alert setup, etc.
0 Comments
Leave a Reply. |