<?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>Architecture on Blog of Christian Felde</title><link>https://blog.cfelde.com/tags/architecture/</link><description>Recent content in Architecture on Blog of Christian Felde</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Tue, 03 Aug 2021 18:19:21 +0000</lastBuildDate><atom:link href="https://blog.cfelde.com/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Don’t use blockchain</title><link>https://blog.cfelde.com/2021/08/dont-use-blockchain/</link><pubDate>Tue, 03 Aug 2021 18:19:21 +0000</pubDate><guid>https://blog.cfelde.com/2021/08/dont-use-blockchain/</guid><description>&lt;p&gt;Rarely do you find technology with so much hype as blockchain, where the best architectural advice is to avoid using it. Or, said with less hyperbole, to correctly minimize your direct dependency on blockchain.&lt;/p&gt;
&lt;p&gt;Why is that?&lt;/p&gt;
&lt;p&gt;Imagine software where thousands of processes all need to look at and verify the same state change. And imagine too that they all need to store a copy of the same information to ensure the state change is correct.&lt;/p&gt;</description></item></channel></rss>