3 ms·
1. I've tended to see slightly better overall performance running multiple VMs (nodes)/server. 2. We use zookeeper and cache locally with an ETS wrapper. It's
by rubyrescue 12y ago
1. I've tended to see slightly better overall performance running multiple VMs (nodes)/server.
2. We use zookeeper and cache locally with an ETS wrapper. It's not-erlang but there are a lot of nice zookeeper tools and the ezk module for erlang is very solid.
3. we typically don't do vpn as if the vpn goes down it is a disaster. dual nics are ideal. i don't always configure that way due to limitations of the environment (non-VPC AWS, for instance). but what are you trying to control? access to the node even if you know the cookie?
- lmb 12y agoThanks for the pointers. Regarding 3), access control was probably not what I was thinking about. More like, how do I use distributed Erlang without allowing everybody access to the node (even without knowing the cookie) and how do I prevent a MITM to snoop on my Erlang traffic. [1] seems to have some decent info on in, I should have researched some more. [1] http://stackoverflow.com/questions/890938/howto-encrypt-erlang-rpc-calls-and-mnesia-replication-and-other-traffic http://stackoverflow.com/questions/890938/howto-encrypt-erla...
- jlouis 12y agoAs for 1. do test! This is not always the case.