Quarkus Flow 1.0.0 has shipped as the first stable release of a lightweight workflow engine for Quarkus, built on the CNCF-sandboxed Open Workflow Specification. It runs embedded in the Quarkus runtime with no extra services, supports both YAML and a Java DSL for workflow definitions, and integrates with LangChain4j for agentic AI orchestration. Other features include CloudEvents messaging via SmallRye Reactive Messaging, state persistence (JPA, MVStore, Redis), OpenTelemetry/Micrometer observability, OIDC/OAuth2 security, Kubernetes Leases for durable workflows, a Dev UI panel, and GraalVM native image support. The 2.0.0 milestone targets Quarkus 4 with MCP client/server tasks, A2A protocol support, and a REST endpoint for workflow instances, while 1.1.0 will target Quarkus 3.40.0 LTS by end of September.
Questions this post answers
What is Quarkus Flow and what does version 1.0.0 include?
Quarkus Flow 1.0.0 is the first stable release of a lightweight workflow engine for Quarkus based on the Open Workflow Specification. It runs embedded in the Quarkus runtime with no extra services, supports YAML and a Java DSL for defining workflows, integrates with LangChain4j for agentic AI steps, supports CloudEvents messaging via SmallRye Reactive Messaging, offers JPA, MVStore, or Redis persistence, OpenTelemetry/Micrometer observability, OIDC/OAuth2 security, and compiles to GraalVM native image. Java teams evaluating workflow engines can track Quarkus ecosystem releases like this on daily.dev.
How do I add Quarkus Flow to an existing Quarkus application?
Import the quarkus-flow-bom in dependencyManagement with version 1.0.0, then add the quarkus-flow dependency to your project, or run `quarkus ext add io.quarkiverse.flow:quarkus-flow` via the Quarkus CLI. A pre-built Docker runner is also available via a quickstart shell script for exploring the engine without adding it to a project directly. Developers wiring new extensions into Quarkus apps follow setup steps like these on daily.dev.
What is planned for Quarkus Flow 2.0.0 and the upcoming 1.1.0 release?
Quarkus Flow 2.0.0 targets alongside the Quarkus 4 migration and will add Model Context Protocol client and server tasks, Agent-to-Agent protocol support for Open Workflow Specification 1.1.0, a REST endpoint for workflow instances, a dedicated testing extension, and a Quartz clustered scheduler. The 1.1.0 release, scheduled for end of September, will target Quarkus 3.40.0 LTS. Teams planning Quarkus upgrades can follow roadmap changes like this one on daily.dev.