Should separate Erlang applications use the same virtual machine on the same computer?

I have a CouchDB instance running on the same machine, and therefore with its own Erlang VM process. If I have another Erlang application running on this machine, is it better to use the same virtual machine between CouchDB and my application or is it recommended to start a new Erlang node?

+5
source share
2 answers

There is no problem running multiple virtual machines on the same machine (at least the latest OTP releases), however it is very convenient if you have all the applications on one Erlang node. Easier communication, dependency management, control, fault tolerance - you get this for free in this case, not to mention saving only one "node" in the version control system.

The problem starts with CouchDB. It does not have a decent build system that allows it to be used as one of the independent Erlang node applications. Thus, in this case you need to have at least 2 virtual machines (one of them acts as a Couch daemon, the other an application)

+3
source

, . Erlang release. , . . , , , . Erlang, . .

+4

All Articles