[erlang-questions] Best practices for distributing an application over erlang?

Scott Lystig Fritchie fritchie@REDACTED
Thu Feb 17 19:53:45 CET 2011

Gregory Haskins <gregory.haskins@REDACTED> wrote:

gh> Long story short(er): I suspect I am just making all of this harder
gh> than it needs to be, and there must be a ton of you who are just
gh> doing similar operations all the time.

Er, it seems to me that you are mixing together two problems:

    1. managing application bugfixes & upgrades
    2. managing distributed application state

Having a whiz-bang way to manage the BEAM files required to do #1 is
usually done by copying the new BEAM files to all the places that they
need to be, then using a. load a module at a time (usually via the
console, for small patches), b. OTP app upgrade (cool but tricky to
coordinate, depending on the app), or c. rolling node stop & restart.

There are other ways to do it, as you were exploring, but they aren't
the sort of things that I'm aware of many (any?) people using in
production.  (Aside from diskless/stateless embedded systems.)  Or I'm
completely misunderstanding your question....


More information about the erlang-questions mailing list