Warning message

  • The service having id "twitter" is missing, reactivate its module or save again the list of services.
  • The service having id "facebook" is missing, reactivate its module or save again the list of services.
  • The service having id "google_plus" is missing, reactivate its module or save again the list of services.
  • The service having id "linkedin" is missing, reactivate its module or save again the list of services.

Track: Architecting for Failure


Day of week:

"Failure is the key to success; each mistake teaches us something" (Morehei Ueshiba) Failure is inevitable. Complex systems are fragile by nature. What approaches can you leverage to build fault tolerant systems? Come learn from leaders in the fields — those who build and maintain complex systems at web scale companies.

Track Host:
Sudhir Tonse
Cloud Pioneer managing Realtime Data @Uber
Sudhir Tonse manages the Realtime Data Intelligence team at Uber. Previously Sudhir managed the Cloud PLATFORM Infrastructure team at Netflix and was responsible for many of the services and components that form the Netflix Cloud Platform as a Service. Many of these components have been open sourced under the NetflixOSS umbrella. Open source contribution includes Archaius: a dynamic configuration/properties management library, Ribbon: an Inter Process Communications framework that includes Cloud friendly Software load balancers, Karyon: the nucleus of a PaaS service etc. Prior to Netflix, Sudhir was an Architect at Netscape/AOL delivering large-scale consumer and enterprise applications in the area of Personalization, Infrastructure and Advertising Solutions. Sudhir is a weekend golfer and tries to make the most of the wonderful California weather and public courses.
10:35am - 11:25am

by Yongsheng Wu
Engineering Manager @Pinterest

In this talk, Yongsheng from Pinterest is going to talk about how to build highly-resilient systems at scale. His talk will cover 5 highly fault-tolerant, battle-tested systems: dynamic service discovery, real-time configuration management, caching, persistent storage, and event processing pipeline. He will also cover failure cases that prompted engineers at Pinterest to build such systems, and how they actually test these systems to make sure that they can gracefully handle those failure...

11:50am - 12:40pm

Open Space
1:40pm - 2:30pm

by Fangjin Yang
Co-Founder @Imply

Running distributed systems in production can be tremendously challenging. In this session, we will cover common problems and failures seen with distributed systems, and discuss design patterns that can used to maintain data integrity and availability when everything goes wrong. We will use Druid as a real world case study of how these patterns are implemented in an open source technology.

Attendees will learn first hand about the multitude of software, hardware, network, and data...

2:55pm - 3:45pm

by Amos Barreto
Director of Marketplace Engineering @Uber

Humans are most often the SPOF of a distributed system. According to Gartner, “Through 2015, 80% of outages impacting mission-critical services will be caused by people and process issues, and more than 50% of those outages will be caused by change/configuration/release integration and hand-off issues”.

This talk will walk the attendees on how Uber's architecture continues to evolve by providing clear isolation, designing gradual release strategies, enabling fast detection and...

4:10pm - 5:00pm

by Nitesh Kant
Senior Software Engineer @Netflix

Netflix with more than 60 million subscribers worldwide and accounting for a third of the internet traffic in the United States, is a highly available internet service. In order to guarantee high availability for our service, we have architected our systems in a way that different failures modes in distributed systems causes graceful degradation and not unavailability.

In our constant endeavor to improve availability of our services, we are on our path to embrace asynchrony in its...

5:25pm - 6:15pm

by Bhakti Mehta
Senior Software Engineer @BlueJeansNetwork

It is well said that "The more you sweat on the field, the less you bleed in war". Failures are an inevitable part of complex systems. Accepting that failures happen, will help you design the system's reactions to specific failures.

This talks on best practices for building resilient, stable and predictable services: preventing cascading failures, timeouts pattern, retry pattern,circuit breakers and other techniques which have been pervasively used at Blue Jeans Network. Join me in...


Covering innovative topics

Monday Nov 16

Tuesday Nov 17

Wednesday Nov 18