immudb
immudb made itself speak Postgres — while its announced v2 rearchitecture sits unfinished.
Comparison · DevOps
NebulaGraph vs pgBackRest
A side-by-side editorial comparison of NebulaGraph and pgBackRest — release velocity, themes, recent moves, and the top alternatives to consider.
NebulaGraph vs pgBackRest: at a glance
What is NebulaGraph?
A graph database spending its releases on query-language parity and traversal speed.
NebulaGraph is a distributed graph database whose recent releases read as steady engine work rather than repositioning. The v3.x line has been filling in query-language gaps — shortest-path variants, INNER JOIN, UDFs, richer rounding and JSON handling — while the bulk of each changelog goes to traversal performance, RocksDB tuning, and Raft/leader-balance stability. Nothing in the entries points at a managed service, an AI/vector story, or a pricing change.
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.
NebulaGraph vs pgBackRest: editorial side-by-side
NebulaGraph
5.0DEVOPS
A graph database spending its releases on query-language parity and traversal speed.
◆ Current state
NebulaGraph is a distributed graph database whose recent releases read as steady engine work rather than repositioning. The v3.x line has been filling in query-language gaps — shortest-path variants, INNER JOIN, UDFs, richer rounding and JSON handling — while the bulk of each changelog goes to traversal performance, RocksDB tuning, and Raft/leader-balance stability. Nothing in the entries points at a managed service, an AI/vector story, or a pricing change.
◆ Where it's heading
The arc is convergence on what users of established graph databases already expect: more of Cypher-like expressiveness, fewer sharp edges under concurrency. Successive releases stack pushdown optimizations (LIMIT into SHORTEST PATH, filters into property fetches) and shave latency in the Meta service, which suggests the pressure is coming from large-deployment operators rather than new-feature demand. Stability items — statement-count limits, plan-tree depth caps, leader-lease fixes — are the recurring theme.
◆ Prediction
Expect the next release to continue the same pattern: another batch of MATCH/GO planner optimizations and one or two query-language additions, rather than a new product surface. The entries give no signal about a v4 line or a hosted offering.
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 NebulaGraph 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 NebulaGraph 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.
Manticore Search
Manticore tags a GitHub release per commit, so the real news is one entry in five.
Vitess
Two patch lines, every release published twice, and no feature news since v24.0.0.
Heroku
Runtime bumps fill the changelog; the managed Postgres line is where Heroku actually moves.
See all NebulaGraph alternatives → · See all pgBackRest alternatives →
Recent activity from NebulaGraph and pgBackRest
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 18d agopgBackRestv2.59.0: PostgreSQL 19 Support
- 29d agoNebulaGraphSingle shortest path, INNER JOIN, and LIMIT pushdown land
- 29d agoNebulaGraphFull-text index overhaul plus parallel RocksDB startup
- 1mo agoNebulaGraphUDF support and a parallel traversal executor
- 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
- 3y agoNebulaGraphCrash fixes in parameter encoding and list functions
- 3y agoNebulaGraphSession killing and a memory tracker for tighter resource control
- 3y agoNebulaGraphPattern predicates in WHERE and CLEAR SPACE arrive
Frequently asked questions
What is the difference between NebulaGraph and pgBackRest?
They serve adjacent needs but don't currently overlap on shipped themes. NebulaGraph is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 NebulaGraph better than pgBackRest?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. NebulaGraph is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 NebulaGraph?
Top NebulaGraph alternatives in DevOps are ranked by recent ship velocity. Browse the "NebulaGraph alternatives" section above for the current picks, or visit /alternatives/nebulagraph 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.