6 ms·
Where do you derive this "almost no one" from? I use it all the time in production, and I guess quite a few other users use it to fulfill their very high uptime
by filmor 6y ago
Where do you derive this "almost no one" from? I use it all the time in production, and I guess quite a few other users use it to fulfill their very high uptime requirements.
- macintux 6y agoI suspect there may be two different features (or degrees of features) here. Hot code reloading is indeed frequently used, but the corresponding ability to upgrade the entire application live (“hot swap”) is less so.
- rkangel 6y agoI don't think so. Hot code reloading is hot code reloading. The parent to your comment is talking about in production so it's the 'real thing'.
- macintux 6y agoI’m not sure what exactly you’re disputing. I would wager that nearly everyone who has run Erlang code in production has upgraded code (edit for precision: a module) live. To engineer the entire application to support an upgrade, and to do all the testing required to make sure it will work correctly, is very resource-intensive, and (lacking real numbers, just from observing the industry working for Basho) I’d wager very few people do so.