3 ms·
VDOM is just a concept that means representing the DOM in code. Texas keeps an elixir data structure representation on the server as a cache of client state an
by toolz 8y ago
VDOM is just a concept that means representing the DOM in code. Texas keeps an elixir data structure representation on the server as a cache of client state and diffs against that. It then pushes a patch up to the clients that is used to update only the parts of the page that have changed
- mandeepj 8y agoVDOM - virtual Dom, right ? > Texas keeps an elixir data structure representation on the server as a cache of client state and diffs against that. Sorry, I don’t think that’s scalable. And, in a load balanced environment, you have to have a central server for this purpose
- toolz 8y agonot true at all. For one 99% of the time people on a realtime updated page will be viewing the same content meaning you can keep a local-only cache that all clients connected to that server can share...that makes the memory footprint negligible...we're talking maybe a few MBs on a typical webapp secondly as far as scaling goes you only need to broadcast extremely small messages (on the order of bytes, not kilobytes) across servers to tell clients to update themselves using their local caches it's extremely scale-able further texas only builds on top of HTTP semantics - meaning it can fall back to a stateless protocol at any point and the user won't even notice other than their app working a bit more slowly (but still working) for a few seconds while the websocket reconnects to a new node