Understanding Your Candidate Application
In order to understand the best possible choices a solutions architect can undertake for an application’s migration and modernization journey, you first need to have a candidate application.
In this case, we will be leveraging a fairly straightforward three-tiered application that is built using legacy .NET code, for example, and backed by Microsoft SQL Server. The application is also connected to a shared file system that allows users to upload data into their respective directories and access them via their internal networks. The application is a monolith by design and does not have too many moving parts. However, it does have the standard networking and security features enabled in the form of a gateway router, a network firewall, and a load balancer.
Figure 19.1 depicts the various components:
Figure 19.1: Typical legacy web application design hosted in a physical data center
The application is...
