scaling a chat application
We are building a chat app with rooms, and we have two tables right now: one for rooms and one for all the messages. On client side we are showing only the messages for the room the user is in by listening to all inserts and filtering for that room's ID. Is this scalable? (maybe some sort of optimization by supabase client)
If not, what should be the approach? Move that filtering to an edge function and stream from it maybe?
2 Replies
Here is some realtime info:
https://supabase.com/docs/guides/realtime/quotas
https://supabase.com/docs/guides/realtime/postgres-changes#database-instance-and-realtime-performance
Realtime Quotas | Supabase Docs
Understanding Realtime quotas
Postgres Changes | Supabase Docs
Listen to Postgres changes using Supabase Realtime.
Thanks,