This article was an attempt to pull the discussion back from slogans to mechanics. Microservices are not hard because the services are small. They are hard because coordination, observability, security, and data integrity get redistributed across the system in ways many teams underestimate.

That is why the piece focused on service discovery, inter-service patterns, transactions, tracing, security, and testing. Architecture decisions get romanticized. Operational consequences do not.

Read the original article.