flâneur

Netflix Microservices - by NK - System Design Newsletter

newsletter.systemdesign.one · 1,035 words · saved by 1 readers

Netflix runs on AWS. They started with a monolith and moved to microservices. Their reasons for migrating to microservices were the following: It was difficult to find bugs with many changes to a single codebase It became difficult to scale vertically There were many single points of failures This post outlines the Microservices lessons from Netflix. 3 main problems with microservices architecture are: Dependency Scale Variance Here are 4 scenarios where the dependency problem occurs: A client request results in a service calling another service. Put another way, service A needs to call service B to create a response. The problem with it is that a failure of a microservice results in cascading failures. The solutions are: Use the circuit breaker pattern to prevent cascading failures. It avoids an operation that will probably fail Do fault injection testing to check if the circuit breaker pattern works as expected. It does it by creating artificial traffic Set up fallback to a static pa

Get my system design playbook for FREE on newsletter signup: This post outlines microservices architecture best practices from Netflix. If you want to learn more, scroll to the bottom and find the references. Share this post & I'll send you some rewards for the referrals. Netflix runs on AWS. They started with a monolith and moved to microservices. Their reasons for migrating to microservices were the following: It was difficult to find bugs with many changes to a single codebase It became difficult to scale vertically There were many single points of failures Microservices benefits…

related reading