realtime VS nhost

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

Supabase Realtime is great for building collaborative applications. You can receive database changes over websockets, store and synchronize data about user presence, and broadcast any data to clients via "channels".

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

Every project is a Postgres database, wrapped in a suite of tools like Auth, Storage, Edge Functions, Realtime and Vectors, and encompassed by API middleware and logs.

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...

As a minor note, one of the linked articles talks about having used RethinkDB for its changefeeds and I made a mental note a bit back that if I ever want that supabase's realtime ( https://github.com/supabase/realtime ) provides something rather like that atop Postgres and I should try that before doing anything clever.

Hasura ❌ (technically yes with Nhost)

Only caveat I say is make sure there's something in it for you; if it's 2 AM it better be mostly for self-benefit. I'm busy constructing a monorepo with the latest technology with NX and pnpm and a half dozen other technologies (I recommend checking out http://nhost.io/); at the end I will build whatever I want and maybe make money. It's not done for the good of someone else exclusively that's for sure

Yeah, I knew of those, I think that's discussed often enough on the dotnet subs. Ory and Zitadel I knew too, but those provide just one thing, and are not native to dotnet. Altough I'll admit, stuff like nhost seem native to typescript but uses go projects under the covers as well.

I'm really digging nhost and apollo-client.

You can use Nhost (100% open source): https://github.com/nhost/nhost/tree/main/examples/docker-compose

Backend Frontend Database pick two or even one. Maybe something like this

I am trying to use basic authentication of nhost.io .

If your backend needs aren't super crazy, i would check out https://nhost.io/