All posts
Case Studies

How Netflix Moved to AWS: Seven Years, No Lift-and-Shift, and What Still Applies in 2026

By

October 25, 2026

6 min read

A three-day database outage in 2008 started Netflix's move to AWS. It finished in January 2016, after rebuilding a monolith into hundreds of microservices, with billing and customer data moved last. What they chose and why, and which of those choices a normal company should copy.

Case Study
Netflix
Cloud Migration
Microservices
Resilience

What happened

  • August 2008: a major database corruption stopped Netflix shipping DVDs for three days. The lesson they drew was to move away from vertically scaled single points of failure such as one large relational database.

  • They chose not to lift and shift, which in their words would have moved all the problems and limitations of the data center into the cloud. They rebuilt instead.

  • All customer-facing services were in the cloud before 2015. Billing and customer and employee data management moved last. The final data center pieces were shut down in early January 2016, seven years in.

  • By then Netflix had eight times as many streaming members as in 2008, viewing had grown by three orders of magnitude, availability was approaching four nines, and cost per stream was a fraction of the data center's, which they called a welcome side benefit rather than the goal.

Want a second opinion on this for your system?

Book a free 30-minute call. You'll leave knowing what we'd do first and roughly what it costs, whether or not you hire us.

What to copy, and what not to

Netflix choice

Copy it?

Why

Rebuild for failure instead of rehosting

For your core systems, yes

Resilience comes from the design, not the hosting

Hundreds of microservices

Usually no

It suited thousands of engineers; a team of 20 is faster with a few well-bounded services

Move billing and sensitive data last

Yes

The highest-risk systems move once the platform and team are proven

Build much of their own tooling

No

Managed services now cover most of what they had to build in 2010

Treat cost as a side benefit

Yes

Migrations justified only on cost tend to be rehosts that save less than expected

hoolco Monthly Review

Once a month: what changed in tech that month and what it means for you, from cloud and AI to security and the tools you build with. Every item links to its source. No sales pitch, unsubscribe in one click.

As of October 25, 2026. Provided as is, for general information, and accurate to the best of our knowledge on the date shown. Not legal, compliance, tax, financial or other professional advice. Prices, limits and vendor services change; check current vendor documentation before relying on anything here. Terms of use.