4 ms·
It’s a bad reorg if it doesn’t take into account on which service(s) which team is working. Also a team sized service is IMHO is a lower bound, not upper bound
by citrin_ru 2y ago
It’s a bad reorg if it doesn’t take into account on which service(s) which team is working.
Also a team sized service is IMHO is a lower bound, not upper bound. I’ve seen a small team working on tens of micro-services and IMHO it is over engineering (but there are exceptions when small micro-services make sense).
- 8n4vidtmkvmk 2y agoYa, my team owns at least 4 services. It's a mess. One is deprecated, one calls the other 2 which just adds latency and redundant data fetches, and neither acts as proper 1st party API (there's always a debate about what service to call when another team wants to integrate with us), and the 4th is some pubsub thing which is invoked a completely different way, so that's one kinda OK. The most annoying part though is we still don't own the entire vertical. There's another 2 services downstream of us, and at least 1 upstream, so we're always at their mercy to accomplish anything.