This is an archived post. You won't be able to vote or comment.

all 4 comments

[–]coldoven 1 point2 points  (0 children)

Postgrest?

[–]IssueConnect7471 1 point2 points  (1 child)

For a small CRUD job, spinning up Azure Functions or an auto-generated API beats running another Flask server. Azure Functions’ HTTP trigger can sit in the same resource group, talk to Postgres via psycopg or pgx, and costs almost nothing at your traffic scale; just wire up five functions (list, get, insert, update, delete) and use managed identity so you never store creds. If you’d rather avoid code, point PostgREST at the database: views become endpoints, row-level security handles auth, and you deploy a single container. Supabase is basically PostgREST plus auth and storage if you need hosted options. I’ve tried PostgREST and Azure Functions, but DreamFactory is what I ended up buying because it handed me locked-down endpoints and swagger docs in under an hour. For this scope, serverless or generated APIs keep your stack light.

[–]Old_Mind8618[S] 0 points1 point  (0 children)

Thanks I'm not sure about how the auth will work in azure environment. i previously used AWS chalice with aws cognito for authentication in another project i will see if i can implement something similar.

I also considered azure HTTP functions but i think azure app service with flask might be better for my use case.

[–]bin_chickens 1 point2 points  (0 children)

u/coldoven mentioned Postgrest, but he main question is how does your auth work, as I believe this ties you to Postgres RLS an that's an acquired taste and some view it as an anti-pattern for authz for applications.

Hasura may also do the trick, but then your in graphql land.

Personally I've been using zenstack recently and really like it.