3 ms·

I believe #2 was the main driver for the supabase team to build their real-time component: https://github.com/supabase/realtime https://github.com/supabase/real

by timwis 3y ago

I believe #2 was the main driver for the supabase team to build their real-time component: https://github.com/supabase/realtime https://github.com/supabase/realtime Background/announcement: https://supabase.com/blog/supabase-realtime-multiplayer-general-availability https://supabase.com/blog/supabase-realtime-multiplayer-gene...

lawik 3y ago
Which as far as I gather uses Phoenix + Erlang distribution to get Phoenix.PubSub going. Which parent was not wanting to do. Funny full circle.
chasers 3y ago
Triggers can affect throughput quite a bit on busy tables. And we didn't want people schemas polluted with triggers. But also we use Erlang distribution and Phoenix.PubSub because with a global network clients connected to the same node in the same region will get normal Broadcast messages to each other faster. If we ran them through Postgres or Redis the added latency wouldn't work for a global thing.