Thursday 20th November, 2014
9:00am to 5:00pm
Using Netflix as a case-study and NetflixOSS components for hands-on practice, learn how to apply reactive principles to application architecture both in the "big" and the "small". Starting at the distributed systems level learn how to handle failure, adapt to changing environments and usage patterns, and iterate quickly in an always-on globally distributed system. Then we'll dive into the code level building blocks of how reactive programming patterns enable fault tolerance and scalability within an application.
Software Engineer on the Netflix Edge Engineering Team
Ben Christensen is on the Netflix Edge Engineering team responsible for fault tolerance, performance, architecture and scale while enabling millions of customers to access the Netflix experience across more than 1,000 different device types. Involved in open-source projects such as Hystrix (https://github.com/Netflix/Hystrix) and RxJava (https://github.com/Netflix/RxJava). Prior to Netflix, Ben was at Apple making iOS apps and media available on the iTunes store.
Author of RxNetty. Works on Netflix's cloud platform team.
Nitesh is on the Netflix's cloud platform team responsible for Netflix's Inter Process Communication stack. Nitesh is primarily involved in the open sourced projects: Eureka (https://github.com/Netflix/eureka), RxNetty (https://github.com/ReactiveX/RxN...) and Karyon (https://github.com/Netflix/karyon).
These libraries form the core of all applications inside Netflix, serving billions of requests per day. Prior to Netflix, Nitesh was one of the early members of apigee (http://apigee.com/) team and created their API platform.
Sign in to add slides, notes or videos to this session