key concept here is micro services architecture

 Another key concept here is microservices architecture, which essentially means breaking down an application into smaller, discrete components that work together as part of the larger system. Among other benefits, microservices allows teams to manage those smaller services independently, rather than having to go back into (and redeploy) the entire application every time a change is necessary. Microservices pair very well with containers, in that each service can be containerized independently. It should be noted that not every existing application makes a great fit for a what is the difference between computer science and computer engineering architecture, and that’s OK.

Some advice from folks who’ve been there: If you’re starting from a largely monolithic application portfolio, don’t approach infrastructure automation as something that will be a short-term project. Instead, think of it as a piece-by-piece process, especially if you’re breaking existing applications into microservices.

“The road to full immutable infrastructure can take time, especially for organizations that have applications that pre-date the proliferation and popularity of container-based applications,” says Michael Fisher, group product manager at OpsRamp. (Editorial voiceover: That means most organizations.) “However, this does not mean that architecture planning and development are at a standstill until the whole application has been configured to run on standalone micro-frontends and backends. Teams should prioritize and containerize services iteratively until the entire application is transitioned.”