A meta-framework for enterprise microservices
Own platformIn active development
The plumbing every company rewrites in every service — API standards, observability, security and build conventions — solved once, versioned and published. A core in plain Java with no framework dependencies, and thin adapters on top of it for Spring Boot, Quarkus and NestJS.
- public repositories
- 30
- stacks supported
- 3
- framework-free core libraries
- 7
How it stacks up
coreplain Java, no framework
api-standardmask-utilsobservability-utilsdate-utilsmapper-utilskeycloakarchitecture-rules
adaptersone wiring per stack
Spring Boot startersQuarkus extensionsNestJS starters
your servicestarts already configured
Maven archetypesGradle templatesreusable CI/CD
- The core depends on no framework: API standards, sensitive-data masking, observability and Keycloak are plain Java; the Spring Boot starters and Quarkus extensions only wire them in.
- The architecture checks itself: ArchUnit tests that enforce Layered, Clean and Hexagonal styles on whoever builds on the platform.
- Three stacks from a single BOM — Spring Boot, Quarkus and NestJS — with versions centralised in one place.
- Observability as a first-class concern: Four Golden Signals and OpenTelemetry tracing wired into the starter, not bolted on later.
- Every decision is written down as an ADR, with semantic versioning and a maturity assessment guide per module.
My role: I design and build the whole platform — the architecture, all 30 repositories, the reusable pipelines and the documentation.