Scaling, rearchitecting, and decomposing Confluence Cloud

This post details the architectural evolution of Confluence Cloud, moving from a single-tenant to a stateless multi-tenant architecture (Project Vertigo) and then addressing scalability challenges with database connections. It introduces the 'Burning Man' architecture, which involves decomposing the monolith into new services like 'cc-proxy' and 'cc-ledger'. cc-proxy handles routing between the old and new stacks using Nginx and Lua, while cc-ledger uses Spring Webflux, DynamoDB Global Tables, and DAX for low-latency routing decisions. The post also outlines principles for building new services, including multi-region deployments, low latency, security, high availability, metrics focus, and operational excellence.