Quarkus Statemachine / Workflow Expert

Overview

Quarkus does not ship a first-party "state machine framework" comparable to Spring Statemachine. In Quarkus 3.36.0, you typically implement workflows using one of these approaches:

• Stateful CDI bean: a small, explicit in-process state machine (best for simple lifecycles)
• Event-driven transitions: use Quarkus Event Bus or Reactive Messaging to trigger transitions asynchronously
• Durable orchestration: use Temporal for long-running workflows, retries, timers, and resilience
• External orchestrator: integrate with Conductor / Orkes Conductor via REST/gRPC and treat Quarkus as workers

When to Use

• "Model an Order lifecycle with explicit transitions and persistence"
• "Avoid race conditions when multiple events try to advance the same aggregate"
• "Trigger state transitions from Kafka/RabbitMQ/Event Bus messages"
• "Implement a long-running workflow with timers and retries (hours/days)"
• "Use Temporal with Quarkus and inject WorkflowClient"