I'be built a few commercial products with it. Overall its pretty awesome, saves me a ton of time. There are some things you end up having to work around that a regular server backend would make easier, but overall its been great for me.
Hey bro, I need some advise, am using GOLANG In the backend and next js as the frontend. Am Using GOLANG jwt auth, and based on that, I used sessions in the frontend. Is that okay?
@@jenny2814. what ? You do know the entire cloud infra is built with Go right ? Docker, Kubernetes. Netflix has services running Go. Dude seriously, stfu. lmao
thoughts on pocketbase vs supabase? seems like supabase might have more features, and I like the easy raw SQL for table definitions (pocketbase has a JSON schema).
Hi Ben! Thanks for testing all those stacks and frameworks on your videos. Right now which stack do you think gives you the best trade between performance, developer experience and features? I've been trying to give Nuxt a go because of the devx and features but I've ended up using Solid-Start on my personal projects lately. Probably because it has more similarities with React which is what I can use at work when I need to do full-stack or client side apps, but I always wonder if I'd end up with a better, faster and cleaner experience with Vue (Nuxt) or Svelte, although I love the component approach of React/Solid with Tailwind/Uno as native HTML/CSS feels dated sometimes
This is the million dollar question I'm working to answer (still don't have the answer sadly), but I think pound for pound I would say any any js meta framework (next, nuxt, sveltekit, solid start, etc), edge runtime, planetscale serverless, drizzle orm, custom auth, vercel hosting, although supabase might end up being really compelling depending on how it feels in production
@@bmdavis419 thank you for the reply! I don't think there's a single answer as it greatly depends on the approach you feel most productive with, it feels so good to find a stack where you can focus on being productive without much sacrifices
Been using supabase as my remote db with nextjs with prisma as the ORM for my side project. Liking it so far. Do you think 500 mb of database space of their free tier is pretty much sufficient?
I have 2 questions: 1. What's the benefit of running supabase locally rather than using their cloud service? 2. Why use drizzle rather than just the supabase SDK?
Not the creator but I used supabase a ton 1. Running locally allows you to test and debug a lot faster, especially with migrations 2. Drizzle is better then supabase cli for a few reason, it doesn't have the postgrest restrictions so you can do complicated nested queries and inserts, it also has much better typescript support, but it doesn't support supabase's rls so you'll need to manage authorization on your own
Currently the big difference is that drizzle works easily on the edge, prisma does not and its much heavier, although I still really like it, definitely gonna make some sort of "its hard to let go of prisma" video soon
Unfortunately supabase is known for being hard to setup locally, there are no available one-click installers which will give you fully featured supabase instances, there are docs about the setup steps, but they require good knowledge of each supabase component and architecture.
It is very much "just postgres", most things are capped in scale by their data layer and postgres scales plenty for me lol, like if I get to the point where postgres is not scaling enough then I have a MASSIVE, very successful app
@@bmdavis419This is VERY TRUE cause soo many devs are stuck with scaling scaling scaling... what are you scaling if you don't have any users eh?? 🤷♂️ and by the time the need to scale comes around, you have an actual reason that will justify hiring specialists to handle the scaling!
@@abdirahmann true, if you have problem with scaling then you wouldnt use supabase in the first place its unreasonable when JS dev talk about scaling on their app
@@bhumit070 you can use livestream or marmot to scale out. Litefs cloud handles this for you if you dont fancy setting it up yourself. But even without this sqlite scales enough for most startups
@bmdavis419 give it a try, you will be glad you did. After I learned how to customize it and create custom endpoints and logic, I find it hard to create my own backend from scratch again lol
Then $10 per thousand, which is definitely not cheap but it’s a pretty painful thing to implement yourself so for a startup optimizing for speed it’s pretty compelling
I also like nHost. Imo it's a notch above Supabase. It's basically Hasura with file storage, auth, real-time, rest api, graphql, serverless functions. It also uses Postgres, has automatic migrations, local environment working with Docker (WSL mandatory if on Windows).
what is the community like? I feel like these all-in-ones sound great, but you eventually encounter bugs that usually lead you to a github issue :( Such was the case with Appwrite.
Very rarely will the choice ever be SQLite? How in the world do you want to scale SQLite? There's also a reason it's "lite", it's not got the same features as something like Postgres.
@@nicolaichristensen6531 When the time comes you can copy your database to PlanetScale and figure out your ways to establish security, auth, email sending and file uploads along with it...
Also like 4GB RAM is enough to serve 500K users and 10_000 concurrent database subscriptions with Pocketbase + Sqlite... And that's before you upgrade to the next larger machine.
You have the skill to provide the best summarization as well as elaboration videos ! Cheers
I've built a couple of projects with it and agree with all points. The fact that you can move your DB out whenever you want is an awesome bonus.
I’m really enjoying it, only learning curve is getting better with stored procedures and row level security
I'be built a few commercial products with it. Overall its pretty awesome, saves me a ton of time. There are some things you end up having to work around that a regular server backend would make easier, but overall its been great for me.
This video was in my recommendations, I'm now subbed
Hey bro, I need some advise, am using GOLANG In the backend and next js as the frontend. Am
Using GOLANG jwt auth, and based on that, I used sessions in the frontend. Is that okay?
Yep thats pretty much what I did in the golang + sveltekit auth video
sweet! i'm definitely interested in drizzle + supabase
Can you please make a video using the ts-rest library? It looks awesome but there is no content on it! Thanks :)
So this is way quicker and easier than writing a backend in go
Its not comparable tho.
you really think you can write a backend in go that works? XD
@@jenny2814. My Go backend works... are you drunk?
@@Kats0unam1 yeah it works because nobody uses it
@@jenny2814. what ? You do know the entire cloud infra is built with Go right ?
Docker, Kubernetes. Netflix has services running Go.
Dude seriously, stfu. lmao
Looking forward to the full deep-dive! (crosses fingers for a Svelte UI)
thoughts on pocketbase vs supabase? seems like supabase might have more features, and I like the easy raw SQL for table definitions (pocketbase has a JSON schema).
Yea I think supabase is better. Way more features, way more power, and a full platform/company supporting it (and sql >>>)
I guess the main appeal of pocketbase is that it is so much more lightweight.
How is the performance on server less function? I’ve ran into issues with getting slow response time with my queries even with pgbouner in the past.
Its been good in my testing, but cold starts are a thing, sadly not able to do edge runtime for our serverside code
The response time of Supabase is too slow and the cache support isn't there yet which can be very good with traditional backends.
Hi Ben! Thanks for testing all those stacks and frameworks on your videos.
Right now which stack do you think gives you the best trade between performance, developer experience and features?
I've been trying to give Nuxt a go because of the devx and features but I've ended up using Solid-Start on my personal projects lately. Probably because it has more similarities with React which is what I can use at work when I need to do full-stack or client side apps, but I always wonder if I'd end up with a better, faster and cleaner experience with Vue (Nuxt) or Svelte, although I love the component approach of React/Solid with Tailwind/Uno as native HTML/CSS feels dated sometimes
Svelte is the best by far.
This is the million dollar question I'm working to answer (still don't have the answer sadly), but I think pound for pound I would say any any js meta framework (next, nuxt, sveltekit, solid start, etc), edge runtime, planetscale serverless, drizzle orm, custom auth, vercel hosting, although supabase might end up being really compelling depending on how it feels in production
@@bradyfractal6653 I don't disagree, although I'm not sure which approach I prefer.
@@bmdavis419 thank you for the reply! I don't think there's a single answer as it greatly depends on the approach you feel most productive with, it feels so good to find a stack where you can focus on being productive without much sacrifices
@@bmdavis419 wouldn't you want custom auth to be handled by clerk or kinde into the nextauth as well ?
Been using supabase as my remote db with nextjs with prisma as the ORM for my side project. Liking it so far.
Do you think 500 mb of database space of their free tier is pretty much sufficient?
Appwrite?
I have 2 questions:
1. What's the benefit of running supabase locally rather than using their cloud service?
2. Why use drizzle rather than just the supabase SDK?
Not the creator but I used supabase a ton
1. Running locally allows you to test and debug a lot faster, especially with migrations
2. Drizzle is better then supabase cli for a few reason, it doesn't have the postgrest restrictions so you can do complicated nested queries and inserts, it also has much better typescript support, but it doesn't support supabase's rls so you'll need to manage authorization on your own
@@isaacfink123 thank you for the response. So Drizzle for the db operations and you'd keep supabase sdks for auth related stuff?
That’s how I’m doing it yep
@@bmdavis419 cool approach! I'll be sure to try it out
I’d like to hear your thoughts on drizzle bs prisma, I’ve been using prisma but have heard good things about drizzle
Currently the big difference is that drizzle works easily on the edge, prisma does not and its much heavier, although I still really like it, definitely gonna make some sort of "its hard to let go of prisma" video soon
Is this supabase self-hosted? How hard was it to set up
This is actually local, I will be deploying to supabase's service
Unfortunately supabase is known for being hard to setup locally, there are no available one-click installers which will give you fully featured supabase instances, there are docs about the setup steps, but they require good knowledge of each supabase component and architecture.
I've never tried to self host supabase but I've heard similar stories of it being hard to setup and require a decent amount of cpu and memory to do so
Same here, github issues is filled with complaints about it
Hey man! Love the videos you make, btw do you have a discord channel? It's high time you make one if not.
What's your take on Neon, Convex, and Pocketbase vs SQLite?
Why not test them yourself ?
Planet scale and neon are both very compelling options as they serve as git for your database which I love
@@Kats0unam1I have no clue about testing that stuff, about how that job is supposed to be done
what is the name of this stack bro
I am terrible at naming things, right now its just sveltekit + supabase lol
fireship calls it the sukit stack 🤓
Supakit
@@bmdavis419 supakit i like that lol
@@anon3118 cool
lets gooooooooo
Hi, what is the font on your vscode?
Jet brains nerd font mono
but how does it scale? i have heard that doesn't scale very well, i mean its built on top of typescript and not something like go(pocketbase)
It is very much "just postgres", most things are capped in scale by their data layer and postgres scales plenty for me lol, like if I get to the point where postgres is not scaling enough then I have a MASSIVE, very successful app
pocketbase wont scale as well due to sqlite
@@bmdavis419This is VERY TRUE cause soo many devs are stuck with scaling scaling scaling... what are you scaling if you don't have any users eh?? 🤷♂️ and by the time the need to scale comes around, you have an actual reason that will justify hiring specialists to handle the scaling!
@@abdirahmann true, if you have problem with scaling then you wouldnt use supabase in the first place
its unreasonable when JS dev talk about scaling on their app
@@bhumit070 you can use livestream or marmot to scale out. Litefs cloud handles this for you if you dont fancy setting it up yourself. But even without this sqlite scales enough for most startups
How would you compare Supabase vs Planetscale?
I can’t give a full honest take yet, these are my first impressions and I’ve yet to use it in prod, once I do there will definitely be a video!
@@bmdavis419 Ok, appreciate what you do!
Wait, it's all postgres?
Always has been.
Indeed.
Supabase vs Convex ?
Does it have hosting like firebase, I can only find it says self hosting for supabase but firebase it actually hosts it for me.
Nah supabase has its entire thing available in a hosted product, it works great I highly recommend
Finally
Bro, a lot of ppl make dall-e wrappers and call it a startup 🤣😂🤣
I guess this is my sign to give supabase a try.
Have you ever tried Strapi?
I’ve never done any serious work with a headless cms before so no, although I hope to in the future
@bmdavis419 give it a try, you will be glad you did. After I learned how to customize it and create custom endpoints and logic, I find it hard to create my own backend from scratch again lol
500 realtime connections only.....
Then $10 per thousand, which is definitely not cheap but it’s a pretty painful thing to implement yourself so for a startup optimizing for speed it’s pretty compelling
@@bmdavis419 at the moment, Deno and convex are my shouts for startup MVP work. Deno deploy and PWA with convex on the backend.
supabase is goated
I also like nHost. Imo it's a notch above Supabase. It's basically Hasura with file storage, auth, real-time, rest api, graphql, serverless functions. It also uses Postgres, has automatic migrations, local environment working with Docker (WSL mandatory if on Windows).
what is the community like? I feel like these all-in-ones sound great, but you eventually encounter bugs that usually lead you to a github issue :( Such was the case with Appwrite.
Nice content brother
Does it offer offline sync?
Supabase has Authentication? … 🧐🤨
is it true that you are a genius?
It is in fact not true, although I wish it was lol
You're still wrong. it's much slower than pocketbase SQLite. 32gb ram can handle 400rps with supabase
Very rarely will the choice ever be SQLite? How in the world do you want to scale SQLite? There's also a reason it's "lite", it's not got the same features as something like Postgres.
@@nicolaichristensen6531sqlite scales extremely well... who cares if the name is "lite", that is a terrible reason to avoid it
@@Dontcaredidntask-q9mNo it does not buddy
@@nicolaichristensen6531 When the time comes you can copy your database to PlanetScale and figure out your ways to establish security, auth, email sending and file uploads along with it...
Also like 4GB RAM is enough to serve 500K users and 10_000 concurrent database subscriptions with Pocketbase + Sqlite... And that's before you upgrade to the next larger machine.
excited for deep dive but u gotta get some sleep bro
I mean, yea lol
I was also concerned about the dark circles, he's the real batman for us hehe
same here😂
database as backend is a bad idea
Why?