Defining Service Boundaries is a really important part of building a loosely coupled system, yet can often be difficult. Here’s one way of realizing where service boundaries lie but looking at Entities and the properties and how they relate. Remember not to fall into the trap of having an entity have to live in one sole location.

🔔 Subscribe: https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw?sub_confirmation=1

💥 Join this channel to get access to source code, demos, and slides!
https://www.youtube.com/channel/UC3RKA4vunFAfrfxiJhPEplw/join

Blog:
https://codeopinion.com/defining-service-boundaries-by-splitting-entities/

Loosely Coupled Monolith:
https://github.com/dcomartin/LooselyCoupledMonolith

📚 Book Recommendations

Domain-Driven Design
https://amzn.to/2QwG8sb

Patterns of Enterprise Application Architecture
https://amzn.to/3d8kMJj

Refactoring: Improving the Design of Existing Code
https://amzn.to/2NVdP5Q

Monolith to Microservices: Evolutionary Patterns to Transform Your Monolith
https://amzn.to/3srUuZ6

RESTful Web Clients: Enabling Reuse Through Hypermedia
https://amzn.to/3d8Q96B

0:00 Catalog Product Model
2:24 Entity as a Service
3:23 Sales Product Model
5:38 Purchasing Product Model
6:34 Available to Promise
9:34 Summary

CodeOpinon: https://codeopinion.com
Twitter: https://twitter.com/codeopinion

#softwarearchitecture #soa #microservices

#softwarearchitecture #soa #microservices #splitting entities #service