In the extreme form, a service-oriented architecture (SOA) ends in microservices; a concept where each service is only responsible for a very limited feature set, therefore with very few reasons to change and is easy to maintain. In terms of domain-driven design, this means that a service is established for each bounded context inside the application. The context can eventually be broken down to mean that each aggregate is managed by separate services. The service managing the aggregate can ensure the inner consistency, and the interface as a service means that the access points are very clearly defined. Most of the problems are shifted to the communication layer, which has to deal with the resilience. This can be a big challenge to the communication layer in the application, and also for the services themselves that now have to deal with more failure modes due to the communication failing between the dependents. Microservices have been used...
JavaScript Domain-Driven Design
JavaScript Domain-Driven Design
Overview of this book
Table of Contents (15 chapters)
JavaScript Domain-Driven Design
Credits
About the Author
About the Reviewers
www.PacktPub.com
Preface
Free Chapter
A Typical JavaScript Project
Finding the Core Problem
Setting Up a Project for Domain-driven Design
Modeling the Actors
Classification and Implementation
Context Map – The Big Picture
It's Not All Domain-driven Design
Seeing It All Come Together
Index
Customer Reviews