AVOID Entity Services by Focusing on Capabilities
Video Statistics and Information
No captions available for this video.
Channel: CodeOpinion
Views: 28,609
Rating: undefined out of 5
Keywords: entity services, software architecture, software design, cqrs, event sourcing, design patterns, software architect, soa, microservices, message queues, event bus, event driven architecture, nservicebus, service oriented architecture, microservice architecture, domain-driven design, enterprise service bus, entitity services, aggregates, entities, business entity services, domain drive design, ddd, micro services, ddd entity, ddd entities, bounded context, Service boundaries
Id: 2gOOstEI4vU
Channel Id: undefined
Length: 7min 30sec (450 seconds)
Published: Wed Feb 17 2021
Please note that this website is currently a work in progress! Lots of interesting data and statistics to come.
On a monolithic application scenario, are this entities supposed to live on Bounded Contexts? Since not all teams are capable of work on a microservices architecture.
Good video, interesting opinion. One question, you're reducing coupling which is great, but arent you introducing complexity in the sense that, now you have to track down where a specific value is living for your product? And what if you need multiple fields for an operation, you have to go to 2 services now instead of 1
In general I don't like video talking about code architecture, as often it ends up with architects astronauts making things worse.
Your video is an exception, well done.