supabase / realtime / 31550675361

91%

push

github

feat: broadcast muster routing (#2073)

* New feature flag to broadcast using Muster's routers instead of always flooding:  `use_muster_broadcast` (which __must__ have the same feature flag bucket key as `use_muster_channel_join`). Only for `broadcast` messages. Postgres Changes and Presence are not touched here.
* For intra region comms we run the Muster scope so we can naturally can find the router and use it to forward to the other nodes.
* For inter region comms we keep a set of `ExHashRing.Ring` (managed by the new `RegionRings` process) of what we expect the membership to be to calculate the router. They might not agree briefly while a rebalance is happening but if a rebalance is happening we would flood anyway and that's what happens. If we send to the wrong node it will just flood the region (and log a warning so we keep track of how often this happens)

96 of 106 new or added lines in 3 files covered. (90.57%)

3675 of 4065 relevant lines covered (90.41%)

4314.81 hits per line