<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Architecture on Michael Hönnig</title><link>https://michael.hoennig.de/en/tags/Architecture/</link><description>Recent content in Architecture on Michael Hönnig</description><generator>Hugo -- gohugo.io</generator><language>en-US</language><copyright>© 2026 Michael Hönnig</copyright><lastBuildDate>Sat, 03 Feb 2018 00:00:00 +0100</lastBuildDate><atom:link href="https://michael.hoennig.de/en/tags/Architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Event-Sourcing - Be complete with your events!</title><link>https://michael.hoennig.de/en/blog/2018/2018-02-03-eventsourcing-be-complete-with-your-events/</link><pubDate>Sat, 03 Feb 2018 00:00:00 +0100</pubDate><guid>https://michael.hoennig.de/en/blog/2018/2018-02-03-eventsourcing-be-complete-with-your-events/</guid><description>In my experimental side-project, Gleanius &lt;a href="https://michael.hoennig.de/en/blog/2018/2018-02-03-eventsourcing-be-complete-with-your-events/#fn-1" &gt;[1]&lt;/a&gt;, a microlearning app, I am using Event-Sourcing &lt;a href="https://michael.hoennig.de/en/blog/2018/2018-02-03-eventsourcing-be-complete-with-your-events/#fn-2" &gt;[2]&lt;/a&gt; and CQRS &lt;a href="https://michael.hoennig.de/en/blog/2018/2018-02-03-eventsourcing-be-complete-with-your-events/#fn-3" &gt;[3, 4]&lt;/a&gt;. This turned out to be an extremely good decision because several times I later found out that new features needed more information in my read model. And the great thing was that in most cases the information was already available in the …</description></item></channel></rss>