Data mesh · reference implementation

A data mesh, on Quarkus.

A working data-mesh reference: a domain of services modeling order-placement-through-shipment, each owning its data, its API surface, and its operational lifecycle, communicating through a deliberate mix of REST, gRPC, GraphQL, and Kafka — backed by Camel-on-Quarkus routes and langchain4j/MCP tooling, with contracts, a catalog, progressive delivery, autoscaling, and full observability.

It rebuilds the Python data-mesh reference as a running Quarkus system — demonstrating data-mesh patterns and Quarkus capabilities side by side, with one runnable Spring Boot twin service for a side-by-side comparison.

What you'll need to run it

JDK 25, Maven 3.9.x, and Docker Engine for the local infrastructure — Kafka, Postgres, and the observability stack. See setup & prerequisites for the full toolchain, including the Quarkus CLI and SDKMAN.

The runnable example tree lives under examples/ in the repo, alongside the demo scripts and the presentation deck.

Demos & examples

Run the reference end to end, then exercise each data-mesh principle and Quarkus capability from a terminal — including the Spring Boot side-by-side comparison.