3 ms·
My answer would be: as big as can be maintained by a "two pizza" team, a group that can have a daily standup etc.. Conway's law exists for a reason. A highly c
by lmm 5y ago
My answer would be: as big as can be maintained by a "two pizza" team, a group that can have a daily standup etc..
Conway's law exists for a reason. A highly cohesive group of people can effectively maintain a highly coupled codebase. When your communication channels with another group are lower-bandwidth, your code-level coupling needs to be lower to reflect tha.
- 6keZbCECT2uB 5y agoStrongly agree. When functionality is in the same service, you can have logs with a reasonable sequence, a shared clock, stack traces, cache consistency, fewer failure points, one commit atomically updates both ends of an interface, etc. Since modularity is lower overhead, you encourage breaking things into smaller pieces with libraries. You can have softer API contracts which enable deleting old code and faster iteration. Turning all software into a distributed system and solving the above problems isn't free, and your productivity is better spent elsewhere unless there's a payoff. Smaller units of deployment, being isolated from implementation changes, etc. are all valuable, but more so across teams than within a team.
- secondcoming 5y agoWhat's that, 4 people? If something 'micro' needs 4 people to maintain it then it probably isn't 'micro' after all.
- lmm 5y agoYeah, I agree with that. People take things like the Amazon platform memo (which was absolutely about having the whole work of a team be presented as one or a handful of services) and take that as a reason to have more services than developers, which is pretty backwards IMO.