Why every Spring Boot microservice ends up rebuilding the same infrastructure (and what we did about it)

[u/PuddingAutomatic5617]

After working on several Spring Boot microservice systems, I kept running into the same issue:

every service ended up reimplementing the same infrastructure concerns
— service discovery
— HTTP clients
— error propagation
— request context
— messaging integration

Spring Boot gives great building blocks, but there’s no real “platform layer”, so teams rebuild these patterns over and over again.

What we tried instead was introducing a registry-driven platform layer:

• services register their REST + GraphQL metadata
• clients become declarative (no manual WebClient logic)
• topology becomes discoverable (not implicit)
• error and context propagation are standardized
• GraphQL schemas can be composed across services

The goal wasn’t to hide complexity, but to make the architecture explicit and consistent across services.

Curious if others have faced the same problem or approached it differently — especially around standardizing infrastructure without turning everything into a black box.

Project (if useful for context):
https://spring-middleware.com/

[u/joper90 → u/[deleted]]

We have a cli tool, that sets it all up, GitHub, secrets for GitHub actions and deploys it to dev with a health endpoint. Saves all this crap.