2012 AWS Latency Tuning 
The Netflix TechBlog
AUGUST 29, 2023
A brief history of IPC at Netflix Netflix was early to the cloud, particularly for large-scale companies: we began the migration in 2008, and by 2010, Netflix streaming was fully run on AWS. These design principles led us to client-side load-balancing, and the 2012 Christmas Eve outage solidified this decision even further.
The Netflix TechBlog
DECEMBER 17, 2019
There are services at Netflix that use RDBMS kind of databases such as MySQL or PostgreSQL via AWS RDS. Passive instances across regions are also possible, though it is recommended to operate in the same region as the database host in order to keep the change capture latencies low. The destination may be a datastore or an external API.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
The Netflix TechBlog
DECEMBER 17, 2019
There are services at Netflix that use RDBMS kind of databases such as MySQL or PostgreSQL via AWS RDS. Passive instances across regions are also possible, though it is recommended to operate in the same region as the database host in order to keep the change capture latencies low. The destination may be a datastore or an external API.
All Things Distributed
OCTOBER 2, 2017
As we began growing the AWS business, we realized that external customers might find our Dynamo database just as useful as we found it within Amazon.com. So, we set out to build a fully hosted AWS database service based upon the original Dynamo design. Manageable – The service would need to be easy to manage and operate.
All Things Distributed
DECEMBER 12, 2013
So when we launched in January 2012, we provided simple query functionality that used hash primary keys or composite primary keys (hash + range). With global secondary indexes in DynamoDB, you can now have many indexes and tune their capacity independently. Since then, we have been working on adding flexible querying.
Expert insights. Personalized for you.
220 
Let's personalize your content