Comparison
Conway's lawvsMicroservice
Conway's law
the system has four services and the company has four teams, and nobody planned that.
Organisations produce designs that mirror their own communication structure. It is an observation rather than advice, and it holds because the interfaces that are easy to change are the ones inside a team and the ones that are hard are the ones between teams. It explains a great deal that looks like bad engineering: an unnecessary service boundary is often just the place where two groups found it easier to define an API than to talk every day.
Full entry →Microservice
the service you own deploys on its own schedule and you have never waited for another team's release.
A service small enough to be owned, deployed and reasoned about by one team independently of the others. The unit of value is independent deployment, not size — a service that cannot be released without coordinating is not buying you anything. The price is real and permanent: every in-process call you replaced is now a network call that can be slow, partial or absent, and every debugging session now spans machines.
Full entry →