3 ms·

Congrats on the launch! I like how you approached adding Storage to the product/platform?, keeping the initial version minimal, yet polished. I've been followi

by iyn 6y ago

Congrats on the launch! I like how you approached adding Storage to the product/platform?, keeping the initial version minimal, yet polished. I've been following you since the public launch and I'm really impressed by your work and progress. Definitely keeping an eye as you go, Supbase is a tool that could fit really nicely in the projects I'm usually working on (fullstack web, mobile apps). I wonder what's your perspective on the GraphQL (and Prisma)? I'm asking, since currently I'm working on a project using Redwood.js, with Prisma on the API layer. Prisma helps a lot with my productivity, as my data model is quite complex, with many relationships/nested queries (read heavy). For the same reason, GraphQL increases my speed on the frontend, since there's just 1 query for nested reads and I don't have to play a requests orchestration game (been there before and it's really slowing down development, at least in my experience). The problem with my current project/setup is that auth, storage, realtime and queues/workers parts are... not ideal and fragmented, as I need to use different providers/servers for each (Auth0, Pusher, dealing with S3 integration, separate server for a worker, since redwood is serverless-first). Focusing on auth, I'm not really satisfied with Auth0 and would love to use something else but only if the migration effort would be worth it. And Supbase looks like something that would make the migration worthwhile, as it solves multiple of my pain points. That's the context behind GraphQL/Prisma question -- right now you're REST-first (which is totally fine, don't want any flamewars REST vs GQL) and I wonder how would that fit in my project, which is very Prisma dependent, with 100% GraphQL API. I have some vague ideas but would love to hear your thoughts here and how you think about GraphQL/Prisma + Supbase mid/long term. Thanks.

kiwicopple 6y ago
We're quite close to the Redwood team - the community there are awesome. > what's your perspective on the GraphQL (and Prisma)? Every Supabase project is a full Postgres instance, so you can connect Prisma to it (we provide the Postgres connection string in the Project Settings). There is a potential issue if you are using serverless functions with Postgres (because connections are expensive in Postgres), but look out for an announcement soon which will solve this ... > I'm not really satisfied with Auth0 and would love to use something else You can also choose to use a single part of Supabase (just the Auth). I'm biased, but I think we are a lot simpler to use. We have a long way to go to catch up to their enterprise offerings though (compliance, SOC2, etc).
- iyn 6y ago
  > Every Supabase project is a full Postgres instance, so you can connect Prisma to it (we provide the Postgres connection string in the Project Settings). There is a potential issue if you are using serverless functions with Postgres (because connections are expensive in Postgres), but look out for an announcement soon which will solve this ... This is the first approach that I could think of, so it's good that you also mention that -- I was slightly worried that I might be missing something. Definitely looking for the mystery announcement :) > You can also choose to use a single part of Supabase (just the Auth). I'm biased, but I think we are a lot simpler to use. We have a long way to go to catch up to their enterprise offerings though (compliance, SOC2, etc). Regarding simplicity, it's something that occurred to me as well and one of the selling points. The happy path for Auth0 is simple enough, but when one has slightly different use-case, it's a tad too complicated for my taste. Fortunately, I don't need enterprise features so I'll experiment with integrating my project with Supabase.

by iyn 6y ago

kiwicopple 6y ago

We're quite close to the Redwood team - the community there are awesome. > what's your perspective on the GraphQL (and Prisma)? Every Supabase project is a full Postgres instance, so you can connect Prisma to it (we provide the Postgres connection string in the Project Settings). There is a potential issue if you are using serverless functions with Postgres (because connections are expensive in Postgres), but look out for an announcement soon which will solve this ... > I'm not really satisfied with Auth0 and would love to use something else You can also choose to use a single part of Supabase (just the Auth). I'm biased, but I think we are a lot simpler to use. We have a long way to go to catch up to their enterprise offerings though (compliance, SOC2, etc).

iyn 6y ago
> Every Supabase project is a full Postgres instance, so you can connect Prisma to it (we provide the Postgres connection string in the Project Settings). There is a potential issue if you are using serverless functions with Postgres (because connections are expensive in Postgres), but look out for an announcement soon which will solve this ... This is the first approach that I could think of, so it's good that you also mention that -- I was slightly worried that I might be missing something. Definitely looking for the mystery announcement :) > You can also choose to use a single part of Supabase (just the Auth). I'm biased, but I think we are a lot simpler to use. We have a long way to go to catch up to their enterprise offerings though (compliance, SOC2, etc). Regarding simplicity, it's something that occurred to me as well and one of the selling points. The happy path for Auth0 is simple enough, but when one has slightly different use-case, it's a tad too complicated for my taste. Fortunately, I don't need enterprise features so I'll experiment with integrating my project with Supabase.