Production is where the money is made and where customers are satisfied – but only as long as 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.
In short: It is not sufficient (anymore) for an application to be “feature complete”, the customers of today expect constant availability and quick response times.
This is a real challenge with today’s complex, distributed and highly interconnected application landscapes which can no longer be handled on infrastructure level but needs to be addressed on application level – 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 you will learn a (small) resilience pattern language organized around some of the core principles of resilience, isolation, loose coupling and latency control – of course garnished with lots of useful tips and tricks.