PocketBase is a Go backend (framework and app) that includes:
And all of this compiles in a single portable executable.
No features have been listed yet.
No PocketBase.io videos yet. You could help us improve this page by suggesting one.
Based on our record, PocketBase.io should be more popular than Patroni. It has been mentiond 78 times since March 2021. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
> I think etcd is basically a k8s only project now I hate etcd with the best of them, but etcd is used in a lot more places than just kubernetes: https://github.com/apache/apisix/blob/master/docs/en/latest/FAQ.md#why-does-apache-apisix-use-etcd-for-the-configuration-center, https://github.com/zalando/patroni#patroni-a-template-for-postgresql-ha-with-zookeeper-etcd-or-consul (this one shows up on HN quite a... - Source: Hacker News / 21 days ago
We have been using stolon + consul for years without issue in our swarm environments. It may also be possible with patroni. Source: 11 months ago
One of the solutions which made it pretty simple for us to run postgresql in a ha environment (mostly in k8s, but works standalone as well) is zalandos patroni: https://github.com/zalando/patroni (docker image: https://github.com/zalando/spilo) we've also tried other operators which were easier to get started, but they failed miserably (crunchyrolls operator is... - Source: Hacker News / 11 months ago
Hello. I am currently using this docker-compose model from Zalando repository. It does not include PgBouncer in its architecture by default. I've been trying to find a containerized implementation involving Patroni, HAProxy, Etcd and PgBouncer. I didn't find anything solid so far. Source: about 1 year ago
General purpose: Patroni - Set up your own etcd + HAProxy + Patroni + Postgres components and it'll generally manage itself after that. Source: about 1 year ago
Solutions like pocketbase and coolify come close to solving these problems. However, I wouldn't choose either as I fear architecture lock-in as much as vendor lock-in. Especially in the case of pocketbase, I may be forced to rewrite my application if it were to scale overnight. - Source: dev.to / 12 days ago
Now, I've released the Gowebly CLI v2.5.0 which includes PocketBase framework/backend support. - Source: dev.to / 14 days ago
Pocketbase [0] is a possibility. It offers a way to subscribe to collections, meaning the client will be notified if any of the records in that collection change. [1] Should be quite efficient too, the FAQ claims that 10k realtime connections on a small hetzner VPS is no problem [2] [0] https://pocketbase.io/. - Source: Hacker News / about 1 month ago
I'd like to plug PocketBase [0] for a similar use case. Last week I was looking for a place to store random data with API access, and was looking at making a Google Sheets backend, but PocketBase was easy and didn't have a 60 rpm quota. Deploying to a cheap VPS was very easy with CapRover. [0] https://pocketbase.io/. - Source: Hacker News / about 1 month ago
I wonder if it is inspired by [1], looks very similar including the "realtime" blurb. -- 1: https://pocketbase.io/. - Source: Hacker News / 2 months ago
Supabase - An open source Firebase alternative
Apache Cassandra - The Apache Cassandra database is the right choice when you need scalability and high availability without compromising performance.
AppWrite - Appwrite provides web and mobile developers with a set of easy-to-use and integrate REST APIs to manage their core backend needs.
Amazon RDS - Easy to manage relational databases optimized for total cost of ownership.
Directus - Free and Open-Source Headless CMS
MariaDB - An enhanced, drop-in replacement for MySQL