Member-only story
Incorporating Resiliency into ‘Legacy’ Spring Boot applications
Site Resiliency Engineering (SRE) is an active topic of discussion these days. As modernization of application platforms is becoming Business As Usual (BAU) it is imperative to understand what SRE is for a developer and how can they contribute to overall health and well being of a critical application platform.
I am not going to start with what is resiliency here — you can refer to my article on that here.
Tactically speaking, coming to the topic of discussion here, we (all) have built applications in the past 5 years even before Docker, Kubernetes (all variations of it on cloud or on-premise), Istio, Nginx, etc., came into vogue. We used none of these platforms to build and deploy critical applications. We also might not have integrated with APM tools (App Dynamics) nor Log monitoring tools such as Datadog or ELK or Splunk.
These are typically JEE/Spring web applications consisting of not-so-micro REST APIs. Typical consumers are SPA Applications or external customers via API Gateway(s) — You can refer to more about my view here. We also might not have implemented resiliency patterns with Hystrix, spring cloud, resilience4j, etc.,
Now you might ask, what should we do now? It might take quite a bit of time for us to do all these things stated above.
