Imagine a world where you do everything within your power to ensure the code you are pushing into production is as ready as possible to take traffic. You have thorough test coverage, you push out canaries, and you use push windows. You have truly operated your microservice in a top-notch way. And then all of a sudden...CPU spikes, GC churns, latency increases, you start spewing errors...enter sad Netflix customers.

This talk will explore ways in which behaviors of other systems result in surprise issues with your service. It will lay out strategies that you can employ to protect your systems and enable your on call staff to sleep better knowing that things will go wrong, but your system won’t fall over.

Key Takeaways:

• Learn how microservice sharding can isolate the impact of outages and enable proper tuning for different use cases.
• Understand the impact of fallbacks on your service and what makes a good fallback.
• Why auto-loading/initializing/binding and package scanning is bad for operations.
• Strategies for “canarying” data changes.