Application development has changed. It might be that you had six weeks to sit, relax the brain, understand the problem domain and come up with an elegant (if monolith) solution by using existing or new skills. You had time to get to know the API you were using, writing code to handle exceptions and errors was a given. Applications then went to the ops team to ensure that anything that you missed or didn’t understand about the deployment environment would be added before the application was production ready. More recently, the pressure is on for developers. Enterprises want applications churned out at a cadence of every couple of weeks that encapsulate business logic in its most basic form, with an expectation that resilience will be provided elsewhere in the stack. Is this really sensible or is there still a need for enterprise grade applications to have built in resilience so they can cope with complex architectures that they are plugging into? We’ll share what is needed for applications to be not only able to cope with past versions of, for example middleware, but that can also be future-proofed to gracefully handle changes or parameters that are as yet uncalled for.