Reverse evaluating Netflix's architecture
Netflix is built on modern, efficient, and robust architectural concepts. Should you follow Netflix's lead and refactor your systems into microservices, split up big databases, and use polyglot approaches? Stefan Toth discusses an inverse architecture evaluation that embarc Software Consulting GmbH conducted to find the answers.
| Talk Title | Reverse evaluating Netflix's architecture |
| Speakers | Stefan Toth (embarc Software Consulting GmbH) |
| Conference | O’Reilly Software Architecture Conference |
| Conf Tag | Engineering the Future of Software |
| Location | New York, New York |
| Date | April 11-13, 2016 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
Netflix is the biggest Internet business in the US. At peak hours, its downstream bandwidth usage climbs to nearly 37% of Internet traffic. Netflix’s success is based on modern, efficient, and robust technologies, frameworks, and architectural concepts. Should you follow Netflix’s lead and refactor your systems into microservices, split up big databases, introduce reactive programming, and use polyglot approaches? Stefan Toth discusses an architecture evaluation that embarc Software Consulting GmbH conducted based on the Architecture Trade-off Analysis Method (ATAM)—but applied in reverse: starting with the known architectural approaches, embarc extracted the most useful requirements and attributes, as well as important trade-offs and constraints. Embarc’s findings illustrate the pros and cons of current technological trends so you can decide how they would fit your own context. Topics include:
