message_bus

Here are a few interesting pieces in Rails specifically: - https://github.com/hopsoft/stimulus_reflex is inspired by Phoenix LiveView and is getting a bit of traction around me - https://github.com/hopsoft/cable_ready is a companion project - https://github.com/discourse/message_bus by Sam Saffron from Discourse is a nice way to implement live updates too, quite easily (video demo at https://twitter.com/thibaut_barrere/status/12565974431075860...) - https://lamby.custominktech.com is a Rails + AWS Lambda integration which is also gaining a bit of traction I also see interesting stuff in Ruby more generally these days: - my own https://www.kiba-etl.org (data processing framework) is growing nicely - https://sidekiq.org is very solid and used in most Rails app I've seen - https://github.com/contribsys/faktory allows interop-jobs (e.g. creat

This is super interesting, I have a very similar project that we use at Discourse https://github.com/SamSaffron/message_bus clearly being an NGINX module nchan is going to be a LOT faster That said there are few little pointers that would make integrating MessageBus with nchan a bit challenging - We have a concept of "reliable pub sub" https://github.com/SamSaffron/message_bus/blob/master/lib/me... this means that if you shut your laptop and then open it stuff just magically catches up with no loss of messages or ordering. Does the redis store you have do something similar (I can not see backing lists in the redis store implementation in store.c) - We implement per-message security, meaning you can publish to a channel/group or channel/user and only those users get the message, I see you can do auth upfront but can per-message security se

This is the alternative: https://github.com/SamSaffron/message_bus/blob/master/lib/me... its significantly less risky, timeouts and raise caused huge amount of pain at scale when I experimented in message bus.