3 ms·

I could be wrong but I don’t think OTP natively implements a load shedding strategy or concurrency controls or request hedging. You would implement a supervisor

I could be wrong but I don’t think OTP natively implements a load shedding strategy or concurrency controls or request hedging. You would implement a supervisor to do so if you don’t want to overload an external system like a DB or microservice (e.g https://github.com/fishcakez/sbroker https://github.com/fishcakez/sbroker).

cpursley 3y ago
Erlang/Elixir is an especially good language runtime for the type of problems you bring up (backpressure, etc)
- kasey_junk 3y ago
  Do you see the circular argument you are making “these libraries are just what otp does natively”. “Here are some things in this library that otp doesn’t do natively.” “You could build a erlang library for that” Having enthusiasm for erlang/otp is fine. It’s a pretty great stack. But there are lots of reasonable reasons not to use it and lots of distributed systems knowledge we’ve picked up since it was designed. Some of which are encoded in libraries like these.