Kartik Agaram pfp
Kartik Agaram
@akkartik
https://world.hey.com/dhh/even-amazon-can-t-make-sense-of-serverless-or-microservices-59625580 feels broadly correct, but has some epicycles. SOA vs microservices is a spectrum, not black and white. Here's a cleaner way I think about things.
1 reply
0 recast
0 reaction

Kartik Agaram pfp
Kartik Agaram
@akkartik
The essential software question of the last 50 years: how to split up the tech parts to minimize communication between people. Teams that talk frequently among themselves should deploy together. Teams that don't need a service boundary so they can deploy separately.
1 reply
0 recast
0 reaction

Kartik Agaram pfp
Kartik Agaram
@akkartik
Among other things, this answers how much utilization to aim for. Every service boundary is a place to introduce slack. If a single team owns too many (>10) tiny services, you get clusters running at 5% utilization. If too many teams share a single service monolith, everyone moves slower.
1 reply
0 recast
0 reaction