pgcat
wal-listener
pgcat | wal-listener | |
---|---|---|
1 | 8 | |
371 | 255 | |
- | - | |
0.0 | 7.0 | |
about 1 year ago | 11 days ago | |
Go | Go | |
Apache License 2.0 | Apache License 2.0 |
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.
pgcat
-
PgCat: Postgres pooler with sharding, load balancing and failover support
You might want to consider a different name, as there's already a pgcat project which appears to be a logical replication extension to augment native logical replication.
https://github.com/kingluo/pgcat
wal-listener
-
Introducing WAL-listener: A PostgreSQL Database Change Notification Service
I would like to introduce my small open-source project, called WAL-listener, available at https://github.com/ihippik/wal-listener This service is designed to keep you informed about any changes occurring in your PostgreSQL database. The core functionality of this service relies on leveraging the Write-Ahead Log (WAL) feature of PostgreSQL. The WAL plays a crucial role in maintaining data integrity within the database. For those interested in understanding WAL better, I recommend referring to the official documentation at https://www.postgresql.org/docs/current/wal-intro.html To receive notifications about database changes, wal-listener utilizes a message broker system. Initially, it supported only NATS as the message broker, but today, I am pleased to announce that Apache Kafka has been added as well, expanding its compatibility. I invite all members to explore and try out this extremely useful service. Your feedback and contributions are welcome!
- A service that helps implement the Event-Driven architecture
-
Transactional outbox. Part II, Message Relay.
Another problem with this approach is that I couldn't find a single library in Go that deals with this, I found one service that is meant to be used for Postgres WAL, you can find it here. I need to try it honestly haven't give it a chance. This approach, this pattern seems so but so hacky(is this a word?), I mean consist literally on dealing yourself or through a library that interact directly with the API of the specific DB you are using. That's not easy, specially if you are just trying to use the pattern to solve a much simpler problem. I would say that there's a lack of libraries that deals with this, maybe in the future that change. Take into consideration that I'm looking this under the perspective of someone that works with Golang, I know in Java the author of the book made a framework for this specific purpose.
- What the heck does line 135 "ProcessLoop:" do in this open source GitHub repo do?
What are some alternatives?
pgcat - PostgreSQL pooler with sharding, load balancing and failover support. [Moved to: https://github.com/postgresml/pgcat]
resgate - A Realtime API Gateway used with NATS to build REST, real time, and RPC APIs, where all your clients are synchronized seamlessly.
odyssey - Scalable PostgreSQL connection pooler
NATS - Golang client for NATS, the cloud native messaging system.
pgcat - PostgreSQL pooler with sharding, load balancing and failover support.
NATS - High-Performance server for NATS.io, the cloud and edge native messaging system.
pgweb - Cross-platform client for PostgreSQL databases
FerretDB - A truly Open Source MongoDB alternative
usql - Universal command-line interface for SQL databases