Break me if you can by Mykyta Protsenko, Alex Borysov

1,999 views · Published 15 November 2018 · 50:37 · Indexed 12 October 2026

Channel: Devoxx · 2018 · Science & Technology

Watch on YouTube

Subscribe to Devoxx on YouTube @ https://bit.ly/devoxx-youtube 
Like Devoxx on Facebook @ https://www.facebook.com/devoxxcom 
Follow Devoxx on Twitter @ https://twitter.com/devoxx

You built your system, you deployed it, you rolled it up in production. Is it the end? No, it’s just a beginning. The life of your system just started. Just like a baby it will grow, evolve and wake you up in the middle of the night.

Usually at this point you start thinking about fault tolerance and error handling. Fault-tolerance concepts sound simple: modern frameworks promise to effortlessly solve it for you. But what is hiding behind the simplicity? Is there anything else that may hurt you? Let’s take a peek, and find out how to design and build truly fault tolerant Java systems.

Let’s make it real by trying failure scenarios against a live system, watching it recover in real-time - and then review the recipes (with gRPC and REST examples) that you can use right away to make YOUR code more resilient and YOUR system more robust.

Mykyta Protsenko From Netflix
Software engineer passionate about all things scalable - from coding to deploying to monitoring. Solid experience in building high-performance backends for a variety of applications in leading Silicon Valley companies: from top-rated social mobile games to billing platforms. Author of Henka (Gradle plugin for Terraform, https://github.com/roku-oss/henka).


Alex Borysov From Google
Software engineer with solid experience in large scale software development. Passionate about software development process and technologies.

Developed trading systems; microservices architecture for World leading social casino games; built infrastructure backend services for a unicorn startup in Silicon Valley with 300+ million users.

Currently working on payments fraud detection infrastructure at Google. Clean coder, test-driven developer.

More from this channel