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.
Paul Bakker is a senior software engineer on the edge developer experience team at Netflix, where he primarily works on tools to increase developer productivity within the company. Besides a love for writing code, Paul has a passion for sharing knowledge. He’s the coauthor of Java 9 Modularity and Modular Cloud Apps with OSGi, both from O’Reilly. Paul is also a frequent speaker at conferences about modularity, container technology, and many other topics. He blogs at Paulbakker.io and tweets as @pbakker.
©2018, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com