Summary

In this chapter, we introduced the example legacy application that we will be modernizing as we progress through the book.

We looked at the infrastructure architecture, which is a typical n-tier design, segregating the data and application tiers with firewalls to lock down traffic to only what is specified as necessary for the application to function. We examined the software architecture of the application, noting that we are combining DDD and MVC architectural patterns to have a well-structured and layered application architecture. We also saw how the software architecture makes use of frameworks such as Spring Boot to simplify and standardize our application and minimize plumbing code.

We then reviewed the application code base to understand how dependencies are managed, how to enable Spring Boot Framework components such as JPA Repository management, and how to override the default decisions and functionality provided by the Spring Boot Framework components. We then...