realtime

Worth mentioning that WAL is enabling and used by Supabase Realtime [0] and WalEx [1] which both are doing very similar thing - polling the WAL changes in order to emit them as Websocket events. I never worked with WalEx but have experience with Supabase Realtime and it is a joy to work with and fits great into the Supa ecosystem. So many layers are disappearing when you rely more on Postgres! [0] https://github.com/supabase/realtime [1] https://github.com/cpursley/walex

Supabase | Senior Elixir Engineer | APAC | Remote | https://supabase.com/ We're hiring to grow our Elixir teams mainly on Supavisor and Realtime projects. You will be using Elixir and also help build new client libs mainly in TS. We work in an opensource manner so you can check our code in https://github.com/supabase/realtime and https://github.com/supabase/supavisor. * Senior Elixir Engineer: https://jobs.ashbyhq.com/supabase/46ffc00b-b9a7-4b45-a6f2-1a... Any question, email me at filipe@supabase.io

Would love to know how this compares to Supabase's realtime. https://github.com/supabase/realtime

This is how a lot of the higher performance pg event streaming libs work. Supabase realtime[0] is a good example. [0]: https://github.com/supabase/realtime

Supabase has arguably a better alternative, which uses logical replication and can be used outside of Supabase. https://github.com/supabase/realtime

You can LISTEN/NOTIFY. Or you can use logical replication and a custom subscriber.[1] Supabase uses the latter.[2] [1]: https://www.postgresql.org/docs/current/logical-replication.... [2]: https://github.com/supabase/realtime

We use :telemetry to collect usage data per tenant for Supabase Realtime. We do this for rate limiting but it also makes it very easy for us to attach a listener (https://github.com/supabase/realtime/blob/main/lib/realtime/...) which ships these (per second) aggregates to BigQuery (via Logflare), which then the billing team can aggregate further to display and actually bill people with.

Yo :D This is what Supabase Realtime does! https://github.com/supabase/realtime Spin up a Supabase database and then subscribe to changes with WebSockets. You can play with it here once you have a db: https://realtime.supabase.com/inspector/new

Where can I learn more about this? I've been thinking of trying to integrate Supabase Realtime (https://github.com/supabase/realtime) into my Django app (without the rest of Supabase), but I'd also like to keep things even simpler if possible. Also, what was the reason not to go with Gevent?

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

How does supabase not qualify as open source? Their stack is primarily comprised of other independent open source projects. The one component that isn't is their "realtime" server that serves updates from postgres' WAL over websockets, but that is open sourced[0] under Apache 2.0. From my understanding the primary part that has not been open sourced is their database browser / web UI. There are plenty of alternative management tools for postgres though. As you can export your database what else would you need to ensure your portability and independence? Granted they make their docs fairly opaque for trying to self host. Presumably to encourage you to just use their hosted service. Hosting open sourced projects seems like a very ecosystem friendly way of monetizing. [0] https://github.com/supabase/realtime

Yes, some portion of their backend is Elixir/Phoenix: https://github.com/supabase/realtime but most of their current stack and active development, frontend and backend, is Next.js, and not the Rails/Phoenix fullstack way: https://github.com/supabase/supabase

Disclaimer - I work on Hasura, so I won't comment too much on which is better. They're all similar flavors of producing realtime results - which take similar, but different, methods to their approach. My understanding (please feel free to correct me if I'm wrong): - Supabase Realtime uses WAL. - Hasura Streaming Subscriptions uses a query which will be append-only (could be a sort-by or also WAL). - Hasura Live Queries uses interval polling, refetching, and multiplexing. - Supabase uses Postgres RLS for authorization, while Hasura uses an internal RLS system which composes queries (which allows for features like the multiplexing above). - All 3 use websockets for their client communication. Supabase Realtime https://github.com/supabase/realtime#introduction https://supabase.com/docs/guides/realtime Hasura Streaming Subscriptions / Live Qu

I contributed to Supabase Realtime [0] before being hired late January of 2021. [0] https://github.com/supabase/realtime/commits?after=9990120c6...