Not to the extreme of fitting everything into one machine but I have explorer the idea of separate stateless workload into its own machine. However, the statel

Not to the extreme of fitting everything into one machine but I have explorer the idea of separate stateless workload into its own machine. However, the stateless workload can still operate in a read-only manner if the stateful component failed. I run an email forwarding service[1], and one of challenge is how can I ensure the email forwarding still work even if my primary database failed. And I come up with a design that the app boot up, and load entire routing data from my postgres into its memory data structure, and persisted to local storage. So if postgres datbase failed, as long as I have an instance of those app(which I can run as many as I can), the system continue to work for existing customer. The app use listen/notify to load new data from postgres into its memory. Not exactly the same concept as the artcile, but the idea is that we try to design the system in a way where it can operate fully on a single machine. Another cool thing is that it easiser to test this, instead of loading data from Postgres, it can load from config files, so essentially the core biz logic is isolated into a single machine. --- https://mailwip.com https://mailwip.com