Part 1
3 chapters
Building data products
How a Quarkus service becomes a self-describing data product — its REST/gRPC surface, its versioned contract, and the planes it moves data across.
04
Services & data products
The anatomy of a data product, order-service as the template built end to end, and inventory/review as further products that demonstrate the pattern varying by role.
05
Contracts & the catalog
Versioned Avro and Protobuf contracts in a shared contracts module and Apicurio registry, and why a discovery catalog is a mesh requirement even though it isn't built yet.
06
The data planes
The asynchronous Kafka backbone and the synchronous GraphQL read layer that federates REST and gRPC — two planes, and why Camel's EIPs are the right lens for the routing logic inside each.