This is how I do it: Erlang manages the distributed portions of my application but a throughput oriented language (such as Haskell) handles the non-distributed

This is how I do it: Erlang manages the distributed portions of my application but a throughput oriented language (such as Haskell) handles the non-distributed portions. A la using the right tool for the job. Cloud Haskell has come a long way but it is still missing Erlang's per-process heaps and scheduler behavior.