Edge PaaS: A Netflix case study about edge service architecture
How do feature teams (device teams, UI, etc.) connect efficiently to backend services in a microservices architecture? How do you create an edge API that satisfies teams with vastly different requirements? And how do you operate these mission-critical edge services? Paul Bakker discusses these challenges and offers an overview of Netflix's PaaS built specifically for edge services.
| Talk Title | Edge PaaS: A Netflix case study about edge service architecture |
| Speakers | Paul Bakker (Netflix) |
| Conference | O’Reilly Software Architecture Conference |
| Conf Tag | Engineering the Future of Software |
| Location | New York, New York |
| Date | February 26-28, 2018 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
Netflix has become the poster child for microservices architecture. Although microservices can solve many problems, they also introduce many new challenges. How do feature teams (device teams, UI, etc.) connect efficiently to backend services in a microservices architecture? How do you create an edge API that satisfies teams with vastly different requirements? And how do you operate these mission-critical edge services? Paul Bakker discusses these challenges and offers an overview of Netflix’s PaaS built specifically for edge services. The highly customized PaaS helps feature teams deploy their own edge services and eases the burden of being on call. There have been multiple iterations of this PaaS. Paul shares the pros and cons of these approaches and some lessons learned the hard way. Paul also outlines the key technologies used to implement the architecture as well as the development process and operations model. Topics include:
