Or just drastically shrink how much data has to be pushed. Static content can be hosted via a CDN to get it close. Serverless workers distributed on a global

Or just drastically shrink how much data has to be pushed. Static content can be hosted via a CDN to get it close. Serverless workers distributed on a global basis running nanoservices backed by Sqlite on the edge that gets way complicated. My favorite sanity test is "distributed transactions". Do you need them? If so how complicated will it be to synchronize all edges when changes comes in from all edges. The usual answer is "we will build that ourselves", then over time the team discovers why it is definite hard problem to solve. You end up reimplementing parts of a database server with added level of complexity. Most architecture should start with "Distributed transactions". Do we need them If so how will we do it. That is just my obsession.