immudb
immudb made itself speak Postgres — while its announced v2 rearchitecture sits unfinished.
Comparison · DevOps
Vitess vs pgBackRest
A side-by-side editorial comparison of Vitess and pgBackRest — release velocity, themes, recent moves, and the top alternatives to consider.
Vitess vs pgBackRest: at a glance
What is Vitess?
Two patch lines, every release published twice, and no feature news since v24.0.0.
The recent window is maintenance on two supported branches: v24.0.2 (34 merged pull requests) and v23.0.5 (35) in late June, preceded by v24.0.1 and v23.0.4 in May. None of these releases describe their contents — each body is a pull-request count and a contributor list, with the actual changelog behind a link. Every release also appears a second time as a `v0.x.y` Go-module tag carrying only a sign-off line.
What is pgBackRest?
PostgreSQL 19 support lands, and pgBackRest stops letting you run most commands as root.
2.59.0 in July added PostgreSQL 19 support and changed a long-standing default: only the restore command may run as root now, with anything else requiring an explicit allow-root. The same release ships a pregenerated distribution tarball so packagers no longer need the code-generation toolchain, and picks up an optional libsystemd dependency. Before it, 2.58.0 concentrated on object storage — HTTP support for S3, GCS and Azure, Azure managed identities, experimental S3 EKS pod identity, and configurable TLS cipher suites.
Vitess vs pgBackRest: editorial side-by-side
Vitess
0.0DEVOPS
Two patch lines, every release published twice, and no feature news since v24.0.0.
◆ Current state
The recent window is maintenance on two supported branches: v24.0.2 (34 merged pull requests) and v23.0.5 (35) in late June, preceded by v24.0.1 and v23.0.4 in May. None of these releases describe their contents — each body is a pull-request count and a contributor list, with the actual changelog behind a link. Every release also appears a second time as a `v0.x.y` Go-module tag carrying only a sign-off line.
◆ Where it's heading
Feature work is concentrated in the majors, not the patches. v24.0.0 at the end of April was the substantive release: window function pushdown for sharded keyspaces, view routing rules, tablet targeting through USE statements, VTGate binlog streaming and structured logging, with external decompressors no longer read from the backup manifest by default. Since then the branches have been in pure upkeep.
◆ Prediction
On the pattern here — a major in April followed by monthly patches on both supported branches — the next thing to expect is continued v23.0.z and v24.0.z patches rather than new capability. The bodies give no indication of what a v25 would contain.
pgBackRest
2.5DEVOPS
PostgreSQL 19 support lands, and pgBackRest stops letting you run most commands as root.
◆ Current state
2.59.0 in July added PostgreSQL 19 support and changed a long-standing default: only the restore command may run as root now, with anything else requiring an explicit allow-root. The same release ships a pregenerated distribution tarball so packagers no longer need the code-generation toolchain, and picks up an optional libsystemd dependency. Before it, 2.58.0 concentrated on object storage — HTTP support for S3, GCS and Azure, Azure managed identities, experimental S3 EKS pod identity, and configurable TLS cipher suites.
◆ Where it's heading
Two currents run through this window. The first is keeping pace with PostgreSQL itself, where support arrives experimentally a release early — PostgreSQL 18 in 2.55.0, 19 in 2.59.0 — so the backup tool is ready before the database is. The second is a steady move toward cloud-native identity and away from ambient privilege: managed identities and pod identity replace stored keys, and the root restriction narrows what a compromised invocation can reach.
◆ Prediction
Given the pattern of adding experimental support one PostgreSQL cycle ahead and hardening defaults as the release lands, the next release is likely to promote PostgreSQL 19 support out of its initial state. The notes do not say whether allow-root will be deprecated further.
Alternatives to Vitess and pgBackRest
Other DevOps products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Vitess or pgBackRest.
Sonic
Sonic is shipping tokenizer control and a dependency diet, two tags at a time.
Postgres Operator
Zalando's Postgres Operator finally shipped v2 — and had to reissue it within a day.
NebulaGraph
A graph database spending its releases on query-language parity and traversal speed.
Manticore Search
Manticore tags a GitHub release per commit, so the real news is one entry in five.
Heroku
Runtime bumps fill the changelog; the managed Postgres line is where Heroku actually moves.
See all Vitess alternatives → · See all pgBackRest alternatives →
Recent activity from Vitess and pgBackRest
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 18d agopgBackRestv2.59.0: PostgreSQL 19 Support
- 1mo agoVitessVitess v24.0.2 patch release (34 pull requests)
- 1mo agoVitessGo-module tag for the v24.0.2 release
- 1mo agoVitessVitess v23.0.5 patch release (35 pull requests)
- 1mo agoVitessGo-module tag for the v23.0.5 release
- 3mo agoVitessVitess v24.0.1 patch release (6 pull requests)
- 3mo agoVitessGo-module tag for the v24.0.1 release
- 6mo agopgBackRestv2.58.0: Object Storage Improvements
- 9mo agopgBackRestv2.57.0: Suppress Repository Symlinks
- 1y agopgBackRestv2.55.1: Bug Fixes
- 1y agopgBackRestv2.56.0: Progress Info Improvements
- 1y agopgBackRestv2.55.0: Verification Improvements and PostgreSQL 18 Support
Frequently asked questions
What is the difference between Vitess and pgBackRest?
They serve adjacent needs but don't currently overlap on shipped themes. pgBackRest is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Vitess better than pgBackRest?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. pgBackRest is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
What are the best alternatives to Vitess?
Top Vitess alternatives in DevOps are ranked by recent ship velocity. Browse the "Vitess alternatives" section above for the current picks, or visit /alternatives/vitess for the full list with editorial commentary on each.
What are the best alternatives to pgBackRest?
Top pgBackRest alternatives in DevOps are ranked by recent ship velocity. Browse the "pgBackRest alternatives" section above for the current picks, or visit /alternatives/pgbackrest for the full list with editorial commentary on each.