pg_auto_failover
roadmap
Our great sponsors
| pg_auto_failover | roadmap | |
|---|---|---|
| 14 | 11 | |
| 1,035 | 187 | |
| 2.0% | 3.2% | |
| 6.4 | 1.7 | |
| 3 months ago | 10 months ago | |
| C | ||
| GNU General Public License v3.0 or later | - |
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.
pg_auto_failover
- 11 Years of Hosting a SaaS
- Streamlining High Availability in PostgreSQL, a Simpler Alternative
-
Why PostgreSQL High Availability Matters and How to Achieve It
pg_auto_failover makes it an absolute breeze. I cannot understand how it's not mentioned in the article.
I've been runnning it for 3 years with great success - https://github.com/hapostgres/pg_auto_failover/discussions/6...
-
Can someone share experience configuring Highly Available PgSQL?
Simplified and probably OK: pg_auto_failover - One Monitor/Witness node and minimum services otherwise. Good documentation to get started and not nearly as complex as Patroni.
-
PG redundancy even in majority failure
There are tools that make managing such a system easier. Check out patroni, pg_auto_failover or PAF
- Just Use Postgres for Everything
-
The C++ Asynchronous Framework
This is /extremely/ uncharitable. It depends more on the project.
For example, both Go and .NET are very well written with comprehensible documentation. Many projects have also been absorbed by the Apache Foundation or other FOSS initiatives.
Every FANG has boat loads of teams working on umpteen different open source packages. The quality naturally varies.
Let me pick two more esoteric projects as a point of comparison.
Yandex Odyssey (https://github.com/yandex/odyssey) an advanced multi-threaded PostgreSQL connection pooler and request router. Figuring out how exactly and when to use this is not quite clear. There is no "getting started" guide for this package. There is barely any explanation for how it works or what it does.
pg_auto_failover (https://github.com/citusdata/pg_auto_failover) run by Citus (owned by Microsoft) monitors and manages automated failover for a Postgres cluster. This repo even has diagrams explaining the workflow and complete instructions.
-
Do you use Percona Distribution for PostgreSQL? How is it working for you?
Right, https://github.com/citusdata/pg_auto_failover has been on my reading list
-
Simpler Postgresql replication setup (NO managed services)
My go to for this is https://github.com/citusdata/pg_auto_failover set up with ansible https://github.com/neuroforgede/pg\_auto\_failover\_ansible
-
pg_auto_failover ile PostgreSQL Cluster Kurulumu
pg_auto_failover github | readthedocs | ytube
roadmap
-
Embeddings: What they are and why they matter
In case anyone is interested, Heroku finally released pgvector support for Postgres yesterday: https://github.com/heroku/roadmap/issues/156
Pgvector is an extremely excellent way to experiment with embeddings in a lightweight way, without adding a bunch of extra infrastructure dependencies.
-
11 Years of Hosting a SaaS
(I work at Heroku) Do you have more details on what sucks? Anything we're not already tracking to fix in our public roadmap? https://github.com/heroku/roadmap/issues
-
Is there any updates as to when Heroku will support IPv6?
"GitHub - heroku/roadmap: This is the public roadmap for Salesforce Heroku services." https://github.com/heroku/roadmap
- Introducing Our New Low-Cost Plans [Heroku]
-
Heroku - If I have a paid dyno can I keep my free ones? (using paid for production, using free for dev and staging)
You can upvote here to try get a version of free back - https://github.com/heroku/roadmap/issues/51
- Let’s try and make free come back
-
Heroku Free Tier
I proposed this -> https://github.com/heroku/roadmap/issues/51 on the Heroku roadmap - hopefully to bring back some sort of free trial environment. Please take a look an upvote if you agree:
- Heroku make their development roadmap public on GitHub
-
Heroku's Next Chapter
The public roadmap is a good idea but highlights how stale the product has become. https://github.com/heroku/roadmap/issues Only now researching adding Cloud Native Build Packs and HTTP2.
This will reaffirm for many the sense that Heroku is being dismantled from within. Feature sunsetting and removal of a free on-ramp doesn't help.
If you're looking for a production alternative to Heroku checkout Northflank.
https://northflank.com
What are some alternatives?
patroni - A template for PostgreSQL High Availability with Etcd, Consul, ZooKeeper, or Kubernetes
cgm-remote-monitor - nightscout web monitor
citus - Distributed PostgreSQL as an extension
piku - The tiniest PaaS you've ever seen. Piku allows you to do git push deployments to your own servers.
orchestrator - MySQL replication topology management and HA
flyctl - Command line tools for fly.io services
postgresql_cluster - PostgreSQL High-Availability Cluster (based on "Patroni" and DCS "etcd" or "consul"). Automating with Ansible.
Dokku - A docker-powered PaaS that helps you build and manage the lifecycle of applications
plv8 - V8 Engine Javascript Procedural Language add-on for PostgreSQL
create-t3-app - The best way to start a full-stack, typesafe Next.js app
discussion
superfly-flyctl