3 ms·
Supabase handles all of this. I handle #1 with by listening to database changes then reacting as needed with a change capture / event-like system: https://git
by cpursley 4y ago
Supabase handles all of this.
I handle #1 with by listening to database changes then reacting as needed with a change capture / event-like system:
https://github.com/cpursley/walex https://github.com/cpursley/walex
- giraffe_lady 4y agoDoes supabase do anything particular to address those or just hand you postgres's RLS? It's been a minute since I used supabase but when I last did you were basically on your own with that. Which is not necessarily bad, RLS is sophisticated enough to handle all real world cases I've come across. But if it's just that I think it's more correct to say postgres already handles all of this.
- discreteevent 4y agoThe problem with event driven systems is that they can end up being a kind of spaghetti. It can be hard to track down all the side effects. There's no place where you can read some code to see what happens sequentially.