3 ms·
>> Microservices are seemingly designed to match the developer’s mental model of their system. Often, services are literally divided by the team who maintains t
by nl 10y ago
>> Microservices are seemingly designed to match the developer’s mental model of their system. Often, services are literally divided by the team who maintains them.
> Good Lord, I sure hope that's not true. Maybe if the non-technical manager designed the system.
Of course it is. It isn't even a terrible way to do it - making a team responsible for their own data end to end does decouple their development velocity from other teams.
It does have problems too of course!
- andrewstuart2 10y agoGood microservices architectures are about data congruity and not team boundaries. Yes, they're hopefully small enough for a single team and may warrant further slicing if they're not, but I definitely would argue strongly against partitioning teams and services into 1:1 relationships. 1:N or 2:N maybe (they should be small enough to quickly learn), but never 1:1.
- nl 10y agoGreat! What about inter-company services? Inter-division? I think your "team:service = 1:N" model above is exactly what happens in many places, and exactly what you seemed to react so strongly to. It isn't exactly uncommon for a data ownership to be aligned with team structure. There are trade-off with all approaches, but I think your initial ("Good Lord, I sure hope that's not true.") comment is an overreaction.