Tutorial: Build a microservice suite

This tutorial takes the modular monolith from the First-app series and splits it across three hosts: a Catalog service, an Orders service, and an Identity service. By the end you’ll have a Kubernetes deploy with shared eventing through Wolverine, OTLP traces that span the wire, and a shared identity provider.

Topology

┌─────────┐        ┌─────────┐        ┌─────────┐
│ Catalog │◄──REST─┤ Orders  ├─event─►│ Billing │
└────┬────┘        └────┬────┘        └─────────┘
     │                  │
     ▼                  ▼
   Postgres          Postgres
                       │
                       ▼
                  Wolverine / RabbitMQ

Status. This tutorial is part of the next docs push (v0.2.0-preview). Until the full walkthrough lands, the reference recipes below already work end-to-end.

Skeleton recipes

• Service-to-service auth — wire Bearer JWT between hosts; see Reference → Configuration → Identity + Technology → Identity. A dedicated Identity tokens tutorial lands in 0.2.0-preview.
• Cross-service eventing — pattern in Event-driven tutorial.
• Shared observability — wire each service to the same OTLP backend; the cephalon.engine.id resource attribute keeps them separated.
• Kubernetes deploy — each host generates its own deploy/kubernetes/ folder; deploy with kubectl apply -k.

What to read in the meantime

• Guide → Concepts → App models — the dimension diagram is the right mental model.
• Technology → Eventing — the Wolverine adapter’s transport options.
• Technology → Identity — service-to-service tokens.
• Source → Kubernetes deployment — apply.ps1 + kustomize layout from the engine source docs (the dedicated Deployment → Kubernetes guide is planned for 0.2.0-preview).

Track progress on the Roadmap or in the tutorials backlog.