Tomasz Skowroński


Software engineer for over a decade with experience in a wide variety of systems (from mobile to financial). Java Virtual Machine languages enthusiast, and the Application Programming Interfaces explorer and traveler. A friend of penguins and androids. Allergic to JavaBeans, but addicted to good coffee beans and clean code. Gamer and a user of audiobooks, podcasts and city bikes.



Resilience patterns in practice (2019)

The resilient system stays responsive in the face of failure. This applies not only to highly-available, mission-critical systems – any system that is not resilient will be unresponsive after a failure. (…) The client of a component is not burdened with handling its failures.The Reactive Manifesto.

A Circuit Breaker isn't a Golden Hammer for resilient development. It is good to know how to help to handle latency and concurrency issues in other ways. During this talk, I will present a fault tolerance assurance concepts. After this presentation you will know more about bulkhead, rate limiter, circuit breaker, retry, fallback and other patterns important for each developer aware of fallacies of distributed computing. Resilience support is important not only for reactive systems but generally for all kind of network software and it needs more developers' attention.