4 ms·
Great read. Similar to my experience with Hasura. Migrations we’re better there but the row level security was a nightmare. Went to just a custom node backend w
by motoxpro 3y ago
Great read. Similar to my experience with Hasura. Migrations we’re better there but the row level security was a nightmare. Went to just a custom node backend with prisma and it’s a dream. No more writing tons of json rules and multiple views just to not query the email field.
Seems like these types of services are good for basic large scale crud applications, probably why you have Hasura pivoting to enterprise.
The quote at the end of going back the future is exactly how I felt. Will never use a Hasura/Supabase/etc again. Just makes things more difficult.
- danielrhodes 3y agoHad a similar experience with Hasura. They have done some amazing things leveraging Postgres and GraphQL. But there were just too many things that got really questionable. Things like migrations becoming inconsistent with metadata, schema lock in, poor ability to do rate limiting, having to use stored procedures for everything, weird SQL that had performance issues, unexplained row level locking, and so on. Local development was a total mess. Ultimately we were making architectural decisions to please Hasura, not because it was in the best interests of what or how we were building.
- motoxpro 3y ago100%. Same things we ran into. Definitely a trap.