<?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>Event-Driven Architecture on Alexis SEGURA</title>
    <link>https://www.alexis-segura.com/tags/event-driven-architecture/</link>
    <description>Recent content in Event-Driven Architecture on Alexis SEGURA</description>
    <generator>Hugo -- 0.143.1</generator>
    <language>en</language>
    <lastBuildDate>Tue, 08 Aug 2023 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.alexis-segura.com/tags/event-driven-architecture/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Key Considerations Learned from Event-driven Architecture Migrations</title>
      <link>https://www.alexis-segura.com/posts/key-considerations-learned-from-event-driven-architecture-migrations/</link>
      <pubDate>Tue, 08 Aug 2023 00:00:00 +0000</pubDate>
      <guid>https://www.alexis-segura.com/posts/key-considerations-learned-from-event-driven-architecture-migrations/</guid>
      <description>&lt;p&gt;Migrating to an event-driven architecture (EDA) can be a difficult task. But it can be a good move for organizations. It can &lt;strong&gt;reduce coupling&lt;/strong&gt;, &lt;strong&gt;improve scalability&lt;/strong&gt;, and &lt;strong&gt;increase the resilience of a backend&lt;/strong&gt;.&lt;/p&gt;
&lt;p&gt;I participated in two migrations to EDA. In the first one, the architecture had several coupling issues. We had a number of microservices with a lot of REST calls between them.&lt;/p&gt;
&lt;p&gt;In the second one, the product was under construction. The team was growing fast. We thought that it was a good move to introduce EDA in the project.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
