zombodb
patroni
zombodb | patroni | |
---|---|---|
23 | 20 | |
4,608 | 6,233 | |
- | 1.5% | |
8.3 | 9.1 | |
25 days ago | 27 days ago | |
PLpgSQL | Python | |
GNU General Public License v3.0 or later | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
zombodb
-
Introducing pgzx: create PostgreSQL extensions using Zig
And lots of interesting extensions use it, like
https://github.com/tembo-io/pgmq
https://github.com/zombodb/zombodb
https://github.com/supabase/pg_jsonschema
-
Create a search engine with PostgreSQL: Postgres vs Elasticsearch
Point 2 is generally solvable via engineering effort and careful dedicated code. From the existing tools, PGSync is an open source project that aims to specifically solve this problem. ZomboDB is an interesting Postgres extension that tackles point 2 (and I think partially point 3), by controlling and querying Elasticsearch through Postgres. I haven't yet tried either of these two projects, so I can't comment on their trade-offs, but I wanted to mention them.
-
Creating an advanced search engine with PostgreSQL
Curious, did you try zombodb? [https://www.zombodb.com/]
-
💃🏼 Quickwit 0.6 released!🕺🏼: Elasticsearch API compatibility, Grafana plugin, and more....
What about zombodb, do you think that quickwit has all the necessary APIs?
-
Write Postgres functions in Rust
No. Haha. Was just the right name for https://github.com/zombodb/zombodb at the time. Software where the only limit is yourself!
- Integrate PostgreSQL and Elasticsearch – ZomboDB
- Postgres Full Text Search vs. the Rest
- ZomboDB: Making Postgres and Elasticsearch work together like it's 2022
-
Postgres Full-Text Search: A Search Engine in a Database
> The hardest part of building any search engine is keeping the index up-to-date with changes made to the underlying data store.
This deserves mention, as it solves that problem: https://github.com/zombodb/zombodb
From the README:
> ZomboDB brings powerful text-search and analytics features to Postgres by using Elasticsearch as an index type. Its comprehensive query language and SQL functions enable new and creative ways to query your relational data.
> From a technical perspective, ZomboDB is a 100% native Postgres extension that implements Postgres' Index Access Method API. As a native Postgres index type, ZomboDB allows you to CREATE INDEX ... USING zombodb on your existing Postgres tables. At that point, ZomboDB takes over and fully manages the remote Elasticsearch index and guarantees transactionally-correct text-search query results.
I find other things also hard in search engines: dealing with the plethora of human languages and all the requirements we may have to processing them. A mature solution like ES therefor is almost a must in the more demanding cases.
-
State of the art for serde-compatible CBOR encoding/decoding?
You can read more about it on our GitHub repo, but basically it brings most of the power of elasticsearch’s searching and analytics abilities straight into Postgres.
patroni
-
Ask HN: Are there any open source forks of nomad smd consul?
> 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/...
https://github.com/traefik/traefik#:~:text=Etcd,
https://github.com/zalando/patroni#patroni-a-template-for-po...
https://github.com/purpleidea/mgmt/tree/0.0.26/etcd (this one shows up on HN quite a bit)
https://github.com/sorintlab/stolon#features
It's actually one of the major reasons I wouldn't touch those projects
-
Citus is not ACID but Eventually Consistent
Citus doesn't provide fault tolerance. Each shard is a monolithic PostgreSQL. To reduce downtime on failures, you can protect each shard with a standby database. As this is a complex configuration, Patroni can help. For this lab I'll use the Citus+Patroni docker-compose-citus.yml from https://github.com/zalando/patroni.git:
-
How to create postgres cluster in docker swarm?
We have been using stolon + consul for years without issue in our swarm environments. It may also be possible with patroni.
-
Why PostgreSQL High Availability Matters and How to Achieve It
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 it's really solid and worked for us for a few years already.
or for k8s their operator: https://github.com/zalando/postgres-operator (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 basically based on the zalando one)
-
Docker: Patroni + HAProxy + Etcd + PgBouncer
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.
-
Can someone share experience configuring Highly Available PgSQL?
General purpose: Patroni - Set up your own etcd + HAProxy + Patroni + Postgres components and it'll generally manage itself after that.
- Patroni Version 3.0.0 Released
- Any self hostable postgres clustering, replication and fail over system?
-
Postgresql HA using repmgr and Keepalived
I don't have a great answer for you except that it sounds like you are trying to create your own version of patroni. Is there a good reason to not just use patroni?
-
Testing Patroni strict synchronous mode 👉🏻 you must handle invisible commit and read split brain
git clone https://github.com/zalando/patroni.git cd patroni docker build -t patroni . docker-compose up -d
What are some alternatives?
pg_search - pg_search builds ActiveRecord named scopes that take advantage of PostgreSQL’s full text search
pg_auto_failover - Postgres extension and service for automated failover and high-availability
Typesense - Open Source alternative to Algolia + Pinecone and an Easier-to-Use alternative to ElasticSearch ⚡ 🔍 ✨ Fast, typo tolerant, in-memory fuzzy Search Engine for building delightful search experiences
stolon - PostgreSQL cloud native High Availability and more.
noria - Fast web applications through dynamic, partially-stateful dataflow
Grafana - The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.
squawk - 🐘 linter for PostgreSQL, focused on migrations
postgresql_cluster - PostgreSQL High-Availability Cluster (based on "Patroni" and DCS "etcd" or "consul"). Automating with Ansible.
stolon-chart - Kubernetes Helm chart to deploy HA Postgresql cluster based on Stolon
helium-etl-queries - A collection of SQL views used to enrich data produced by a Helium blockchain-etl
crunchy-proxy - PostgreSQL Connection Proxy by Crunchy Data (beta)