Production is where the money is made and where customers are satisfied – but only if our application is up, running and responsive. If our application is down or latent, it’s worthless – and even worse, we loose money and reputation.
This is a real challenge with today’s complex, distributed and highly interconnected application landscapes – and concepts like cloud computing or microservices make it even more challenging.
That’s what resilience is about: how to design applications that they are highly available and responsive – even in the face of unexpected failure and load situations.
In this session we will focus on a resilience pattern language that is organized around recovery and mitigation, the core domains of error handling after they have been detected. To complete the picture we will add a few error prevention patterns – everything of course garnished with lots of useful tips and tricks.