<?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 Personal Blog of Maximilian Ehlers</title><link>https://blog.sodawa.com/tags/architecture/</link><description>Recent content in Architecture on Personal Blog of Maximilian Ehlers</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><lastBuildDate>Fri, 07 Jul 2017 18:53:00 +0000</lastBuildDate><atom:link href="https://blog.sodawa.com/tags/architecture/index.xml" rel="self" type="application/rss+xml"/><item><title>Multi Tenant React.js starter</title><link>https://blog.sodawa.com/blog/multi-tenant-react-js-starter/</link><pubDate>Fri, 07 Jul 2017 18:53:00 +0000</pubDate><guid>https://blog.sodawa.com/blog/multi-tenant-react-js-starter/</guid><description>Let me start this article with the requirements that it is going to adress, so you know if you want to continue.
You have multiple tenants (websites) the clients should share components between each other to increase development speed of new tenants SSR has to be supported build configs are the same, but can be extended Since these are quite a few things and a lot of good stuff is already open source I am only going to focus on what needs to be added onto the great react-starter-kit.</description></item><item><title>Frontend Microservices</title><link>https://blog.sodawa.com/blog/frontend-microservices/</link><pubDate>Fri, 19 May 2017 18:52:00 +0000</pubDate><guid>https://blog.sodawa.com/blog/frontend-microservices/</guid><description>Frontend Microservices With this article I want to show you the basic idea behind Microservices on the Frontend, or at least how I understood it.
The first thing to do is set up a small skeleton website that I will divide visually into 3 parts that each have some content. For this I am using the new CSS Grid functionality.
Here is a Screenshot (and the files if you want to follow along):</description></item></channel></rss>