<?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>EIP on Ricardo Zanini</title><link>https://ricardozanini.github.io/tags/eip/</link><description>Recent content in EIP on Ricardo Zanini</description><generator>Hugo</generator><language>en</language><lastBuildDate>Fri, 09 Oct 2026 18:32:50 -0400</lastBuildDate><atom:link href="https://ricardozanini.github.io/tags/eip/index.xml" rel="self" type="application/rss+xml"/><item><title>Quarkus Flow and Apache Camel Are Not Competing: Here's Why</title><link>https://ricardozanini.github.io/2026/10/09/quarkus-flow-and-apache-camel-are-not-competing-heres-why/</link><pubDate>Fri, 09 Oct 2026 00:00:00 +0000</pubDate><guid>https://ricardozanini.github.io/2026/10/09/quarkus-flow-and-apache-camel-are-not-competing-heres-why/</guid><description>&lt;p&gt;People see a fluent Java DSL in Quarkus Flow and a fluent Java DSL in Apache Camel and assume the two projects are going after the same problem. They are not. One manages the lifecycle of a process — decisions, waits, retries, AI agents. The other moves data between systems. They solve different problems, and in a well-designed system you may find yourself using both.&lt;/p&gt;
&lt;p&gt;This post breaks down why.&lt;/p&gt;</description></item></channel></rss>