You are viewing content from a past/completed QCon

Presentation: Graceful Degradation as a Feature

Track: Architecting for Success when Failure is Guaranteed

Location: Broadway Ballroom North, 6th fl.

Duration: 2:55pm - 3:45pm

Day of week: Wednesday

Share this on:

This presentation is now available to view on InfoQ.com

Watch video with transcript

Abstract

The move from monolith to microservice has allowed pieces of functionality to be deployed individually and on demand. Having functionality isolated allows the opportunity for one microservice to fail without bringing down the whole system.

However, it also increases complexity with the number of API calls being made across all of these services. Each service has unique failure models, whether its a database, cache, queue, etc. How can you be sure that one single failure doesn’t cause an outage for your end users?

Landing the launches of new products and features and providing your users with a positive experience is crucial to your success. If something is to fail, you’d prefer they didn’t know. Or if they did, it shouldn’t interrupt their experience.

In this talk, we’ll cover graceful degradation as an engineering goal which can be confidently tested with Chaos Engineering. By purposely causing failure of one service at a time in a controlled environment, you can safely observe the effect on the end user, whether that’s on a laptop browser, a mobile app, or the result of an API call.

Speaker: Lorne Kligerman

Director of Product @GremlinInc

Lorne currently leads the product team at Gremlin, helping companies avoid outages by running proactive chaos engineering experiments. He last worked at Google Cloud as a Product Manager on App Engine, empowering developers to build applications on a fully managed and resilient platform.

Find Lorne Kligerman at

Proposed Tracks

  • Trouble-Shooting in Production

  • Disrupting Technology on Wall Street

  • Resilience vs Failure in Architecture

  • The Weeds of Distributed File Systems

  • Organizational Agility

  • Product & Customer Focused Teams

  • Just Culture (Blameless Culture)

  • Modern CS in the Real World

  • Architectures You’ve Always Wondered About

  • Machine Learning and AI in the New Decade

  • Evolving Java - Including K8s/Containers, Kotlin and Impact on AOT

  • Ethical Considerations in Software

  • Microservices and Scalability

  • Container Slinging

  • Native Compilation Is Back (A Look at Non-Vm Compilation Targets)