In this chapter, we discussed the microservice architectural style in detail, its history, and how it differs from its predecessors, monolithic architecture, and SOA. We further defined the various challenges that monolithic architecture faces when dealing with large systems. Scalability and reusability are some definite advantages that SOA provides over monolithic architecture.
We also discussed the limitations of monolithic architecture, including scaling problems by implementing a real-life monolithic application. The microservice architecture style resolves all of these issues by reducing code interdependency and isolating the dataset size that any one of the microservices work upon. We utilized dependency injection and database refactoring for this. We also further explored automation, CI, and deployment. These easily allow the development team to let the business sponsor choose which industry trends to respond to first. This results in cost benefits, better business response, timely technology adoption, effective scaling, and the removal of human dependency. Finally, we discussed Azure Service Fabric and got an idea about Service Fabric and its different programming models.
In the next chapter, we will go ahead and transition our existing application to microservice-style architecture and put our knowledge to the test. We will transition our monolithic application to microservices by discussing the new technology stack (C#, EF, and so on). We will also cover the concept of seam and discuss microservice communication.