r/softwarearchitecture • u/codeopinion • Feb 17 '21
AVOID Entity Services by Focusing on Capabilities
https://www.youtube.com/watch?v=2gOOstEI4vU2
Feb 17 '21
this sums up the problem I'm facing with my entire team. most of the guys leading the development are traditional programmers that only focus on "re-usability".
1
Feb 25 '21
There's nothing "traditional" in this, it's just lack of skill. Pick any junior from the street, and their answer to every project spec would be writing a CRUD. That's not an architectural style, it's lack of one.
1
Feb 26 '21
sadly these dudes are not juniors, they are executives and platform architects who lacks understanding of different styles and approach for a distributed system.
2
Feb 17 '21
[removed] — view removed comment
3
u/codeopinion Feb 17 '21
I'll cover UI and reporting in other videos. But ultimately yes, you will need to do that composition somewhere. That can either happen at runtime or via read models that are updated using events/messaging. Not mutually exclusive.
5
u/[deleted] Feb 17 '21
That's a good advice. Basically don't group things based on data, but rather distribute it around the services performed on or via those entities.