3 ms·

I think probably yes. In Erlang world though you get so much for free with beam that it changes your worldview a bit. Say you're writing, I dunno, a spring boot

I think probably yes. In Erlang world though you get so much for free with beam that it changes your worldview a bit. Say you're writing, I dunno, a spring boot api to expose some db records as a service and suddenly this api is getting hot on the network... Now you need more than one of them, so suddenly state comes into play, maybe sessions, and so on.. With Erlang, you can take your single node app and reasonably trivially make it run on 30 nodes.. There are gotchas, of course, but the quote is quite good: "Any sufficiently complicated server backend contains an ad hoc, informally-specified, bug-ridden, slow implementation of half of Erlang."

jolux 5y ago
I think the key insight in Erlang/OTP is that it should be easy to make any part of your application asynchronous and highly concurrent. Not only can you spread an application trivially across many servers, but even within a single server boundary you can take a GenServer and make as many copies of it as you want. you can break up any application into a set of processes communicating with each other asynchronously with not very much effort, which can make breaking it up and scaling it onto more servers easier when you eventually need to. OTP makes highly concurrent applications a joy to write.