Poor man’s islands architecture

<p>Sometimes you don&rsquo;t need much to enjoy yourself on a nice island surrounded by the ocean of static content.</p> <p>The islands architecture is all the rave now. Some believe it&rsquo;s the answer to all questions and a solution to all issues. Right now, I&rsquo;m working on a project of learning and comparing six of the more talked-about frameworks (I&rsquo;ll write about that once I&rsquo;m done), and one of them is an implementation of the islands architecture. Since I&rsquo;m new to that topic, I decided to read about it. As part of my effort to understand the concept, I wrote a simple component islands loader, and I&rsquo;ll share it with you here.</p> <p>If you&rsquo;re new to the islands architecture, seeing the loader code may help you understand what it&rsquo;s about and how it works. Many authors make it sounds like it&rsquo;s rocket surgery, but it&rsquo;s really a simple (and effective) concept that shouldn&rsquo;t really lose its value just because it can be explained simply.</p> <p><strong>UPDATE:&nbsp;</strong>The loader code was made shorter and simpler by using the dynamic&nbsp;<code>import()</code>.</p> <p><a href="https://betterprogramming.pub/poor-mans-island-architecture-cbcb0ac45092">Read More</a></p>