> Markdown version of [/videos/100214-20-years-of-solving-unsolvable-problems?t=1093](https://www.wearedevelopers.com/videos/100214-20-years-of-solving-unsolvable-problems?t=1093). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md). --- # 20 Years of Solving Unsolvable Problems How do you synchronize global databases when the CAP theorem says it's impossible? By deploying atomic clocks, AWS spent 20 years solving unsolvable constraints through invisible engineering. - **Speakers:** [Werner Vogels](https://www.wearedevelopers.com/@werner-vogels) - **Event:** World Congress 2026 Europe - **Published:** July 10, 2026 - **Duration:** 31:58 - **URL:** https://www.wearedevelopers.com/videos/100214-20-years-of-solving-unsolvable-problems ## Summary For over two decades, AWS has scaled by refusing to accept industry defaults, repeatedly turning impossible constraints into global infrastructure. Early hyper-growth revealed that commercial relational databases could not handle internet-scale key-value operations, resulting in the creation of Dynamo and sparking the NoSQL movement. Beyond technical execution, AWS shifted the global software landscape by replacing prohibitive upfront licensing with a pay-as-you-go economic model, putting the power of predictable scaling directly in developers' hands. The core of this transformation relies on what is termed "invisible engineering" — the vast, unseen architectural work required to make powerful abstractions feel effortless. For instance, eliminating the conventional virtualization tax required redesigning the hypervisor stack. By shifting DOM zero, networking, and security to dedicated hardware via the AWS Nitro System, developers gained bare-metal performance with uncompromised isolation. When building event-driven serverless architectures with AWS Lambda, the team realized overcoming cold-start latency demanded radical new approaches. This led to Firecracker microVMs and AWS SnapStart, which leverages S3 caching to drastically reduce JVM initialization times. Pushing the boundaries of distributed systems also meant challenging long-held limits, such as the perceived impossibility of accurate time synchronization outlined by the CAP theorem. By deploying atomic clocks, satellite networks, and the open-source ClockBound toolkit to calculate hardware drift, accurate microsecond timestamping became a reality for global database tables. Ultimately, the most significant achievements in software are remarkably quiet. True operational excellence stems from professional pride in building secure, resilient systems, ensuring things are done properly even when nobody is watching. **Keywords:** AWS nitro system architecture, distributed systems time synchronization, serverless cold start latency, AWS firecracker microvms, AWS snapstart optimization, dynamo key-value data modeling, hypervisor virtualization tax, cloud infrastructure economics, event-driven compute frameworks, amazon time sync service, clockbound hardware drift, CAP theorem limitations, invisible engineering practices, bare-metal performance scaling, NoSQL database evolution ## Chapters 1. **Operating at unprecedented scale in the early days** (00:05) — How outgrowing commercial software limits forced early engineering teams to design custom distributed systems. 1. **The database outage that inspired the creation of Dynamo** (02:30) — Investigating a massive holiday outage revealed that data was largely non-relational, leading to the creation of Dynamo. 1. **Productizing internal APIs and revolutionizing cloud economics** (05:38) — Launching an infrastructure service transformed the IT industry by introducing a pay-as-you-go economic model. 1. **The crucial role of invisible engineering in systems** (09:06) — Why the most critical operational work, like continuous security and predictable performance, remains unseen by users. 1. **Building AWS Nitro to eliminate the virtualization tax** (11:25) — Eliminating the hypervisor bottleneck and Dom0 vulnerabilities by moving virtualization and IO to dedicated hardware. 1. **Evolving serverless compute with Firecracker and SnapStart** (18:13) — Developing open-source microVMs and snapshotting features effectively eliminated cold starts for latency-sensitive serverless applications. 1. **Bringing accurate time synchronization to global distributed systems** (23:36) — Solving the impossibility of accurate time in distributed systems by wiring microsecond hardware clocks directly into server instances. 1. **Taking professional pride in invisible engineering work** (30:03) — Why developers should prioritize rigorous operational excellence even when the outside world cannot see their effort. ## Related Moments - [Discussing history and enterprise adoption of serverless](https://www.wearedevelopers.com/videos/34-serverless-past-present-and-future) (from "Serverless: Past, Present and Future") - [Solving complex platform architecture challenges at an enterprise scale](https://www.wearedevelopers.com/videos/1209-coffee-with-developers-maria-apazoglou) (from "Coffee with Developers - Maria Apazoglou") - [Final performance results and key architectural takeaways](https://www.wearedevelopers.com/videos/733-accelerating-authentication-architecture-taking-passwordless-to-the-next-level) (from "Accelerating Authentication Architecture: Taking Passwordless to the Next Level") - [Speaker background and the vision for cybernetic transformation](https://www.wearedevelopers.com/videos/1614-ai-augmented-devops-with-platform-engineering) (from "AI-Augmented DevOps with Platform Engineering") - [Hiring passionate software engineers to tackle unprecedented scaling challenges](https://www.wearedevelopers.com/videos/100128-the-golden-age-of-email-owning-the-inbox-in-the-age-of-ai) (from "The Golden Age of Email: Owning the Inbox in the Age of AI") - [Resolving resource scaling challenges with dynamic serverless deployments](https://www.wearedevelopers.com/videos/1008-serverless-java-in-action-cloud-agnostic-design-patterns-and-tips) (from "Serverless Java in Action: Cloud Agnostic Design Patterns and Tips") ## Related Articles - [Developers vs Scammers, Bad Design, AI is Pointless, AJAX is 20 and more - The Best of LIVE 2025 - Part 1](https://www.wearedevelopers.com/magazine/661-developers-vs-scammers-bad-design-ai-is-pointless-ajax-is-20-and-more-the-best-of-live-2025-part-1) - [What is Software Engineering in the Age of AI?](https://www.wearedevelopers.com/magazine/640-what-is-software-engineering-in-the-age-of-ai) - [Dev Digest 120 - Apple and peers](https://www.wearedevelopers.com/magazine/455-dev-digest-120-apple-and-peers) - [Dev Digest 101 - the XXX edition](https://www.wearedevelopers.com/magazine/382-dev-digest-101-the-xxx-edition) ## Related Jobs - [Software Engineer, Identity](https://www.wearedevelopers.com/jobs/ext/1713561-software-engineer-identity) at **Twilio** - [Principal Software Engineer](https://www.wearedevelopers.com/jobs/ext/149130-principal-software-engineer) at **Twilio** - [Software Engineer L3](https://www.wearedevelopers.com/jobs/ext/1840587-software-engineer-l3) at **Twilio** - [Artificial Intelligence (AI)](https://www.wearedevelopers.com/jobs/ext/1952055-artificial-intelligence-ai) at **Twilio** - [Principal Software Engineer](https://www.wearedevelopers.com/jobs/ext/267591-principal-software-engineer) at **Twilio** - [Software Engineer L2 - Cloud Infrastructure](https://www.wearedevelopers.com/jobs/ext/1282024-software-engineer-l2-cloud-infrastructure) at **Twilio**