It's rare that a big company in a highly-competitive market will write about how they build and run their website, and Ben Christiansen on the Netflix Tech blog continues a series of articles about how the Netflix website works.
In an earlier post by Ben Schmaus, we shared the principles behind our circuit-breaker implementation. In that post, Ben discusses how the Netflix API interacts with dozens of systems in our service-oriented architecture, which makes the API inherently more vulnerable to any system failures or latencies underneath it in the stack. The rest of this post provides a more technical deep-dive into how our API and other systems isolate failure, shed load and remain resilient to failures.
Tidbit from the story: The Netflix API gets more than a billion API calls per day.