4 ms·
I have no experience with Erlang, but wouldn't ABENDing one or both of the sending / receiving actors if a queue spills over be entirely consistent with both th
by ShroudedNight 4y ago
I have no experience with Erlang, but wouldn't ABENDing one or both of the sending / receiving actors if a queue spills over be entirely consistent with both the model described and the finite nature of real systems?
I'm also curious about this:
> ...crash-only software makes it impossible to assert any guarantees on a callstack.
What sort of guarantees are we talking about here?
- Joel_Mckay 4y agoI would recommend: "Designing Elixir Systems with OTP: Write Highly Scalable, Self-Healing Software with Layers" ( James Edward Gray, II, Bruce A. Tate ) Erlang, and its simplified Elixir wrapper language can allow a OTP child process to continually crash while remaining operational for other users. Some tend to get irritated by the idea of graceful fail back code. Again, something a dead-letter queue in RabbitMQ handles rather trivially. Have a wonderful day. =)