2 ms·
Yes, it definitely can be. LiveView will create real problems when the user is many hops from the server. I say this as someone who has gone all in, but current
by te_chris 6y ago
Yes, it definitely can be. LiveView will create real problems when the user is many hops from the server. I say this as someone who has gone all in, but currently we're UK based and only serving the UK market. Multi-region scaling for liveview will certainly be 'interesting'.
- ksec 6y agoThx. I really hope Phoenix team will provide a sort of default way for Multi-Region Set up. Just thinking about that complexity cause me headache.
- ecmascript 6y agoCan't you put a load balancer in front of several elixir servers? So that the load balancer can point you to whichever is closest. Then just share the database connection between these elixir servers.
- Existenceblinks 6y agoNot straightforward as it sounds. Where is a center for all of those nodes? The edge server part is easy with Fly.io, but distributed "problem" and latency are still not great for realtime application selling worldwide. The latency between the edge servers and the database server will give you bad UX with current "mount/3 gets called twice" strategy. Going from edge to db twice is really bad in my experience. Now you would think about adding read-only postgresql nodes on at least 3 nodes (US, EU, and Asia), $$$$.
- raihansaputra 6y agoI don’t have any experience about scaling Multi-region, but I think for these kinds of ‘apps’, the way to keep response times down is to have multi-region DB and servers. Is that true?
- ecmascript 6y agoInteresting, can you elaborate somewhat? What is the type of issues you are facing? Isn't the issues pretty much the same for normal single page apps as well? Most single page apps require data loads for many actions causing maybe not interface latency, but rather data load latency.