Home › Best prompts › #11

Prompt #11Turn everything into microservices, we'll figure out why later

“Split this monolith into 47 microservices. We'll figure out why later.”

655,201 uses · Architecture · Kubernetes

What Claude replies (roughly)

$ kubectl get pods
47 pods Running, 0 customers
// latency: +400%, cloud bill: +1,200%
// fits the target architecture (probably)

Observed consequences

• A 12-line function becomes 3 services, 2 message queues and 1 weekly meeting.
• The “legacy” monolith is already missed by everyone.
• The architecture diagram no longer fits on one screen, or two.

Verdict

47 services, 1 developer, 0 explanations.

Recommendation: Splitting a monolith into microservices adds operational complexity (network, observability, data consistency, teams). Justify each boundary by a need for evolution or load, not fashion; otherwise you pay the cost without the benefit.

Other popular prompts

• Adapt all of this to the target architecture
• Add the whole stack, it's easy with Claude
• It's easy, just do it with Claude

Inspect my repo →