<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Event on Rowanto Luo</title><link>https://log.rowanto.com/categories/event/</link><description>Recent content in Event on Rowanto Luo</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Thu, 09 Jun 2016 23:35:11 +0000</lastBuildDate><atom:link href="https://log.rowanto.com/categories/event/index.xml" rel="self" type="application/rss+xml"/><item><title>Event Driven Architecture</title><link>https://log.rowanto.com/posts/event-driven-architecture/</link><pubDate>Thu, 09 Jun 2016 23:35:11 +0000</pubDate><guid>https://log.rowanto.com/posts/event-driven-architecture/</guid><description>
&lt;h2 id="why-do-we-need-it"&gt;
Why do we need it?
&lt;a href="#why-do-we-need-it" class="h-anchor" aria-hidden="true"&gt;#&lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;In the early stages of the development, event driven architecture is not needed since everything is still small and could still be contained in one place. Unfortunately, as the system grows bigger and bigger, putting everything in one place is not a very good way to scale (a.k.a monolith). The logic of the whole system will also keep increasing in complexity, and eventually there will arise the need to separate the giant system into domains.&lt;/p&gt;</description></item></channel></rss>