Solution architecture
Whether you’re planning to migrate an existing application to microservices or adopt a microservice architecture from scratch, there are some important architectural decisions that you need to make upfront. In this section, we’ll discuss some of the key architectural principles for how we define a microservice and its components.
The use case presented previously has a monolithic solution that uses one SQL Server database, with multiple backups every day. The services share the same data model because every web API service targets the same data:
Figure 4.3 – Monolithic solution architecture
Our healthcare solution uses a traditional three-tier application architecture; the client applications include mobile applications and web applications. The presentation layer includes .NET Framework 4.5, and we also have Xamarin.Forms, Web App Model-View-Controller (MVC), and AngularJS, as well as mobile applications built...
