This approach is pretty interesting - I’d love to read about implementing Erlang-style availability in other languages.
https://github.com/becls/swish
Another in Gambit Scheme, but it hasn't been touched in a while:
Some more info on riak.org about the current story regarding who maintains would help me a lot in choosing it.
To me Riak was the only noSQL scale-out-able data store product that really made sense.
- telecoms, as it was specifically designed for telecoms.
- "glue" in networked applications: to orchestrate, pass messages around and the like. See GitHub [1] or CoD [2] etc.
In a sense, chats are a mix of both. Erlang is rarely a good fit in pretty much anything else.
[1] https://www.infoq.com/interviews/erlang-and-github/
[2] https://www.erlang-factory.com/upload/presentations/395/Erla...
Really? I am not sure I trust this claim.
I'm biased in that I've been heavily involved in the project, but I will stand by the five years of five nines availability claim.
[1]: http://martinsumner.github.io/presentations/spine2_erlang#/2...
> There is no better example of Erlang’s reliability than the English National Health Service (NHS). [...] Using Riak (written in Erlang), the NHS has managed 99.999% availability for over five years.
From what I could find out, NHS's Spine2 is mostly Python, with "a bit" of Erlang and Javascript. They do use Riak, but they also use Redis, RabbitMQ, Python/Tornado, Ubuntu and lots of other components.
This sentence could have said "Using redis (written in C)", or "Using Tornado (written in Python)", and still be fully correct.