27 February 2018
you read up on CQRS and whiteboarded your microservices. The time has to come to release and you are brimming with confidence.
But once you are live the pain starts coming; deadlocks in the Db, servers that begin queuing requests and then fail, users reporting errors you have never seen.
Keeping an application alive in production takes more than just good practices. You have to understand stability patterns like retry and circuit breaker, you have to understand what it means to be a multi-user system if you don't want deadlocks, you need to understand what happens if you lose a node and you need to know how to monitor your application in production so you can understand the pain when it hits you.
In this presentation we explore some of the key patterns you need to know to keep your application alive in production.
By the end of the session you should have a far better idea of what you need to know to stay up.