<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Event-Driven on Mateusz Cholewka</title><link>https://mateuszcholewka.com/categories/event-driven/</link><description>Recent content in Event-Driven on Mateusz Cholewka</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Wed, 20 Aug 2025 10:45:24 +0200</lastBuildDate><atom:link href="https://mateuszcholewka.com/categories/event-driven/index.xml" rel="self" type="application/rss+xml"/><item><title>Beyond the Hype: Why We Chose Redis Streams Over Kafka for Microservices Communication</title><link>https://mateuszcholewka.com/post/why-we-chose-redis-streams-over-kafka/</link><pubDate>Tue, 19 Aug 2025 00:00:00 +0000</pubDate><guid>https://mateuszcholewka.com/post/why-we-chose-redis-streams-over-kafka/</guid><description>&lt;p>I&amp;rsquo;m writing this article based on my personal experience implementing a production-ready solution using Redis Streams with my team. This is a result of a few months working with Redis Streams, development and maintenance. If you&amp;rsquo;re not sure, which solution to choose, I hope this article helps you choose the best solution for your needs.&lt;/p>
&lt;h2 id="introduction">Introduction&lt;/h2>
&lt;p>The problem we were facing was quite common. The question was how to communicate between two microservices in a simple, fast, and reliable way. Our first thought was to choose between two of the most popular solutions: RabbitMQ or Kafka. We wanted something that could handle higher throughput in the future, so it seemed, that Kafka would be better choice. It met all of the above requirements, and it&amp;rsquo;s also a resume-friendly solution.&lt;/p></description></item></channel></rss>