2012 Design Latency Tuning 
The Netflix TechBlog
AUGUST 29, 2023
Today we have a wealth of tools, both OSS and commercial, all designed for cloud-native environments. To improve availability, we designed systems where components could fail separately and avoid single points of failure. There is a downside to fetching this data on-demand: this adds latency to the first request to a cluster.
The Netflix TechBlog
DECEMBER 17, 2019
Designed with High Availability in mind. We designed the framework to minimize database impact. 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. Dumps can be taken any time, via a provided API.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
The Netflix TechBlog
DECEMBER 17, 2019
Designed with High Availability in mind. We designed the framework to minimize database impact. 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. Dumps can be taken any time, via a provided API.
All Things Distributed
OCTOBER 2, 2017
With these requirements in mind, and a willingness to question the status quo, a small group of distributed systems experts came together and designed a horizontally scalable distributed database that would scale out for both reads and writes to meet the long-term needs of our business. This was the genesis of the Amazon Dynamo database.
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