Elixir in Depth – Reading and personal notes

Re:Elixir in Depth – Reading and personal notes by macintux on Thursday August 17, 2017 @11:42AM (#15037758)

Code hot swapping is not particularly friendly at all. It's impressive that you can, but the time required to write the code carefully enough and QA the upgrade doesn't seem to be worth it for most applications.

Sure, a telco switch that has to be up 24x7, hot swapping makes a lot of sense. Most applications can spare the brief downtime to reload the old-fashioned way (or have multiple servers to allow upgrades to be done without downtime).

[ Parent | on HN ]

Re:Elixir in Depth – Reading and personal notes by defined on Thursday August 17, 2017 @07:44PM (#15042112)

I'm sorry, I disagree.

Code hot swapping can often trivially be done (by simply compiling and copying the fixed module, then 'l(module)' in the shell) if the module does not change the state record or break function signatures. I have used this countless times to fix a module function with no downtime. You don't always need the full code upgrade procedure, which is indeed far more onerous.

[ Parent | on HN ]

Re:Elixir in Depth – Reading and personal notes by macintux on Thursday August 17, 2017 @08:07PM (#15042241)

I agree, I should have been more specific. Individual module upgrades are indeed straightforward. That didn't sound like what the poster was describing.

[ Parent | on HN ]