Hacker News Reader

Comment by abtinf | Hacker News Reader

There are so many projects I could use pocketbase for, if only it supported Postgres.

I get the philosophical reasons behind why it doesn’t and why it’s SQLite only.

It’s just that in a corporate environment, I could trivially deliver full production ready applications because there is a team that handles all the Postgres replication/failover/ha/dr/backups/recovery for me. Pocketbase with pg would be super simple to deploy to a pod, getting 95% of production readiness done.

View on HN

> There are so many projects I could use pocketbase for, if only it supported Postgres.

So... you want Supabase? which is what Pocketbase is inspired by.

It's not single binary, you need to spin up a dozen or so containers and have a full DevOps team on standby if self hosting.

Well yeah, that's the nature of using something like Supabase it is designed to scale and be flexible to develop on top of.

Yes, OP wants to hand the database to their team.

No. OP said they want to handle the database to their team. They didn't say anything about the auth, analytics, admin dashboards, real time change data management proxies, connection poolers to their team. Your modern backend as a service that's not pocketbase usually has a dozen moving parts.

Most enterprise teams have plug and play SQL databases ready to go, anything else would require more work with DevOps.

I am also building similar product but with different approach And just using SQLite for now but plan on adding Postgres support ( orm I am using supports it ) … but nowhere near production ready. Due to buzz around products like litestream I feel like just SQLite is also viable nowadays. I also have own cdc based replication thing wip but yeah just having fun stage

https://github.com/blue-monads/potatoverse

Supabase? https://supabase.com/

like others have said, try sup abase

https://supabase.com/docs/guides/self-hosting/docker

i havent tried self hosting but it doesn't look too tricky

setup is easy but you're stuck with one instance. they stripped all multi-tenant features and even the selfhosted version is missing essential features, scaling is off the table though.

It's at least a starting point, since it's just a few different services and a docker-compose you can set up your own scaling. It's not like Pocketbase has multi-tenant or is able to scale OOTB either.

Reply on news.ycombinator.com