Definitely check out "choose your comfort level"[1].
> PostgREST's limitations also had me going back to an API server architecture because I definitely didn't want to write logic in database functions.
Because of PostgREST's philosophy[2], you're expected to write database functions(not necessarily SQL, since PostgreSQL offers many PLs).
So if you're not comfortable with that, you can treat PostgreSQL just as a data store and pair it up with your favorite ORM. Supabase doesn't force you to use PostgREST.
> PostgREST's limitations also had me going back to an API server architecture because I definitely didn't want to write logic in database functions.
Because of PostgREST's philosophy[2], you're expected to write database functions(not necessarily SQL, since PostgreSQL offers many PLs).
So if you're not comfortable with that, you can treat PostgreSQL just as a data store and pair it up with your favorite ORM. Supabase doesn't force you to use PostgREST.
[1]: https://supabase.com/docs/guides/getting-started/architectur...
[2]: https://postgrest.org/en/latest/#database-as-single-source-o...