5 ms·
>The static-location model seems like the right place to start, since it is at least capable of expressing all the types of distributed systems we might want to
by dingnuts 2y ago
>The static-location model seems like the right place to start, since it is at least capable of expressing all the types of distributed systems we might want to implement, even if the programming model offers us little help in reasoning about the distribution. We were missing two things that the arbitrary-location model offered:
> Writing logic that spans several machines right next to each other, in a single function
> Surfacing semantic information on distributed behavior such as message reordering, retries, and serialization formats across network boundaries
Aren't these features offered by Erlang?
- chuckledog 2y agoGreat point. Erlang is still going strong, in fact WhatsApp is implemented in Erlang
- shadaj 2y agoErlang (is great but) is still much closer to the static-location (Actors) paradigm than what I’m aspiring for. For example, if you have stateful calculations, they are typically implemented as isolated (static-location) loops that aren’t textually co-located with the message senders.
- prophesi 2y agoYep, the words fault tolerance and distributed computing immediately brings to my mind Erlang/Elixir.
- deleted 2y ago[deleted]