* Still good if you work with Elixir
* Good if you have, say, RabbitMQ or Riak in your stack
* Fred knows his stuff.
* Still good if you work with Elixir
* Good if you have, say, RabbitMQ or Riak in your stack
* Fred knows his stuff.
I'd also love to see something from the other angle: taking a program that's already an instantiation of a complex, distributed architecture, written in e.g. C, and then rewriting it in idiomatic Erlang (or Elixir—especially with GenStage/Flow stuff) to reduce its code size while retaining the same distributed-system properties as its ancestor system.
Remsh and recon are tools I use almost every day.
Chapter 3 planning for overload is useful in general not just for Erlang systems, and is something that is not given enough consideration usually.
In particular the 'fuse' type stuff is really important when you have a real world system where "let it crash!" is not really ok, because you have, say, a user interface, or a web server that should not be part of everything just crashing. In particular, something I've seen: if your Erlang application talks to a database, and the database goes down for some reason, it may be desirable to have the whole application not go down with it!
Thank you!