Microservices Under Scrutiny: Insights from Musk’s Critique and the Pitfalls of Architectural Fads

Elon Musk’s recent comment questioning the value of microservices sparked a wave of discussion, especially among those who have long championed the approach. While the author admits limited knowledge of Twitter’s internal architecture, they agree that microservices may be over‑used and that Musk’s claim that only 20% of services are valuable lacks scientific backing.

The piece emphasizes that every technology has a dual nature: the strengths of monolithic applications become the weaknesses of microservices and vice‑versa. Therefore, no architecture is universally superior; decisions should be context‑driven.

Examples are given of organizations forcing microservice adoption without clear justification—such as a government procurement document mandating microservices for a low‑traffic environmental platform, or a client pressured to refactor a stable monolith into microservices merely to satisfy a vendor’s expectations. The author humorously suggests wrapping the monolith in Spring Cloud and exposing a few dummy services to appease such demands.

Quoting Brooks from *The Mythical Man‑Month*, the author reiterates that there is no silver bullet in software engineering; concepts become popular because they are fashionable, not because they solve all problems.

To avoid being locked into a single architectural pattern, the author proposes the notion of “open capability” as an autonomous unit that can be composed flexibly, allowing teams to defer concrete technology choices and maintain architectural openness.

The discussion expands to other service granularity ideas—macro services, mini services, and even nano services (functions)—highlighting that microservices are just one point on a spectrum.

Drawing a parallel with the rise and fall of the “mid‑platform” (中台) trend, the article notes how enterprises once rushed to build centralized platforms only to later abandon them when the buzz faded, illustrating the cyclical nature of technology fads.

Finally, the article mentions the upcoming IDCF DevOps Hackathon (Feb 25‑26, 2023, Hangzhou) that combines lean startup, agile development, and DevOps pipelines, inviting both corporate teams and individuals to participate.