4 ms·
Supabase's Realtime [1] is one of the solutions that can help with that. Although it doesn't exactly let you LISTEN at scale, but it allows the applications to
by gurjeet 5y ago
Supabase's Realtime [1] is one of the solutions that can help with that. Although it doesn't exactly let you LISTEN at scale, but it allows the applications to be notified on changes in the database.
> Listen to changes in a PostgreSQL Database and broadcasts them over WebSockets
[1]: https://github.com/supabase/realtime https://github.com/supabase/realtime
Disclosure: I'm a Supabase employee.
- seanwilson 5y agoHow many connected users does this scale to roughly?
- cpursley 5y agoConsidering that it's Elixir/Erlang, presumably millions: https://phoenixframework.org/blog/the-road-to-2-million-websocket-connections https://phoenixframework.org/blog/the-road-to-2-million-webs...
- killingtime74 5y agoDoes Supabase have HA or failover yet? Asked a few months ago and got no answer
- cpursley 5y agoI like Supabase's approach over pub/sub. One of the big advantages is they listen to the Postgres WAL which overcomes the 8000 bytes limitation[1] of the notify approach. And Elixir is especially well suited for this type of workload. I actually extracted out much of the Supabase Realtime library so that I could work with the data directly in Elixir[2] [1]: https://github.com/supabase/realtime#why-not-just-use-postgresqls-notify https://github.com/supabase/realtime#why-not-just-use-postgr... [2]: https://github.com/cpursley/walex https://github.com/cpursley/walex