My mental model is that all queueing systems with pub/sub features are OTP-lite or OTP-wannabes.
Are you saying that Erlang just does it more efficiently to the extent that scale isn't an issue for the concern/solution?
https://raft.github.io/raft.pdf
An overview of why this replaced many traditional non-durable queue use-cases in RabbitMQ:
https://www.youtube.com/watch?v=wuZC7m6dCDA
https://www.rabbitmq.com/docs/quorum-queues
What are Elixir/Erlang channels:
https://hexdocs.pm/phoenix/channels.html
What types of problems channels are used to solve:
https://felt.com/blog/pheonix-channel-routing-patterns
Have a great day, =3
My mental model is that all queueing systems with pub/sub features are OTP-lite or OTP-wannabes.
Are you saying that Erlang just does it more efficiently to the extent that scale isn't an issue for the concern/solution?