<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Kogito on Ricardo Zanini</title><link>https://ricardozanini.github.io/tags/kogito/</link><description>Recent content in Kogito on Ricardo Zanini</description><generator>Hugo</generator><language>en</language><lastBuildDate>Wed, 19 Aug 2026 16:04:15 -0400</lastBuildDate><atom:link href="https://ricardozanini.github.io/tags/kogito/index.xml" rel="self" type="application/rss+xml"/><item><title>From Apache KIE SonataFlow and Kogito to Quarkus Flow: Migrating to Open Workflow 1.0</title><link>https://ricardozanini.github.io/2026/08/19/from-apache-kie-sonataflow-and-kogito-to-quarkus-flow-migrating-to-open-workflow-1.0/</link><pubDate>Wed, 19 Aug 2026 00:00:00 +0000</pubDate><guid>https://ricardozanini.github.io/2026/08/19/from-apache-kie-sonataflow-and-kogito-to-quarkus-flow-migrating-to-open-workflow-1.0/</guid><description>&lt;p&gt;If you have been running Kogito Serverless Workflows in production, you are likely aware that the landscape has shifted. The specification evolved from version 0.8 to 1.0.0, the project was &lt;a href="https://openworkflow.cloud/blog/general/announcing-rename-to-open-workflow-specification/"&gt;renamed from Serverless Workflow to Open Workflow Specification&lt;/a&gt;, and the runtime engine moved from Apache KIE to the Quarkiverse. This is not a minor version bump — it is a fundamental paradigm shift in how workflows are defined, moving from explicit state declarations to task-based orchestration.&lt;/p&gt;</description></item></channel></rss>