Summary

We walked through the difference between building a traditional monolith application and how a microservice-based architecture can add value to large complex applications. Now, you know how a cross-functional team can help deliver software faster using DevOps and other practices. Distributed computing has its own challenges and the solution is to not think of it as an afterthought, but instead make it part of your requirement.

We saw how microservices are made by decomposing a monolith into functional capabilities. This requires an understanding of the domain, which helps build the bounded context for our domain model. We also covered a few of the disadvantages of using this as a silver bullet, as one-size-fits-all is certainly not true.

Microservices can be considered a subset of SOA. Using this architecture for large applications has many benefits such as a lower learning curve due to a smaller code base. This allows for refactoring within short time frames. Testing of inpidual services can be done without having to run a large test suite for the entire application.