Should Erlang systems (or anything running on the BEAM VM) be monolithic, i.e. everything running in the same distributed application, or should they be split into multiple microservices like any python/go/c++ shop would do? Since each process in Erlang has its own memory space, it seems like they behave like microservices internally, and thus, a single Erlang application should be enough, but maybe there's something I've overlooked? 
Should Erlang systems be monolithic?
architecture;microservices;erlang