A few weeks ago, I gave the first in a series of planned talks on the topic of NoSQL @ Netflix. By now, it is widely known that Netflix has achieved something remarkable over the past 2 years — accelerated subscriber growth with an ever-improving streaming experience. In addition to streaming more titles to more devices in both the US and Canada, Netflix has moved its infrastructure, data, and applications to the AWS cloud.
In the spirit of helping others with similar needs, we are sharing our experiences with AWS and NoSQL technologies via this tech blog and several speaking appearances at conferences. Via these efforts, we hope to foster both improvements in cloud and NoSQL offerings and collaboration with open-source communities.
The NoSQL @ Netflix series specifically aims to share our recommendations on the best use of NoSQL technologies in high-traffic websites. What makes our experience unique is that we are using publicly available NoSQL and cloud technology to serve high-traffic customer-driven read-write workloads. Once again:
Netflix’s NoSQL Use-cases = public NoSQL + public cloud + customer traffic + R/W workload + high traffic conditions
The slideshow below was loosely based on the following whitepaper. Some of the key questions addressed by the slides and whitepaper are as follows:
- What sort of data can you move to NoSQL?
- Which NoSQL technologies are we working with?
- How did we translate RDBMS concepts to NoSQL?
Driven by a culture that prizes curiosity and continuous improvement, Netflix is already pushing NoSQL technology and adoption further. If you would like to work with us on these technologies, have a look at our open positions
The slides are available here:
— Siddharth “Sid” Anand, Cloud Systems
Originally published at techblog.netflix.com on March 31, 2017.