← Back to home
Comparison · DevOps

Barman vs Erlang/OTP

A side-by-side editorial comparison of Barman and Erlang/OTP — release velocity, themes, recent moves, and the top alternatives to consider.

Barman vs Erlang/OTP: at a glance

FeatureBarmanErlang/OTP
SectorDevOpsDevOps
Velocity score0.05.0
Sparks · 30d00
Top themespostgresql, backup, object-storage, incremental-backupruntime, security, ssh, tls
Last editorial update2h ago1h ago
WebsiteVisit →Visit →

What is Barman?

Barman is finishing its move from a backup host to a cloud-native lifecycle.

EnterpriseDB has spent the last four releases rebuilding Barman around object storage. 3.18.0 added block-level incremental backups direct to cloud with only a small staging area on the Barman host; 3.19.0 closed the loop with cloud restore and a dedicated cloud-wal-restore command. Encryption and compression restrictions on incremental backups were removed in 3.14/3.15, and the release notes are unusually detailed — each change carries a rationale and a BAR- ticket reference.

Read the full Barman trajectory →

What is Erlang/OTP?

Three OTP branches move as one release train, and SSH and epmd carry the security load.

Erlang/OTP is patching three branches in lockstep — 29 as current, 28 and 27 as maintenance — with each fix set published as a trio within minutes of itself. The window is dominated by security work in the network-facing applications: OTP 29.0.4 carried six CVEs including an epmd denial-of-service mitigation, and the 4 August trio brought SSH into line with RFC 4253 by rejecting packets not aligned to the cipher block size, with a timing-safe packet-discard path for CBC ciphers. A regression in the previous patch that stopped epmd binding to localhost was fixed in the same trio.

Read the full Erlang/OTP trajectory →

Barman vs Erlang/OTP: editorial side-by-side

B
Barman
DEVOPS
0.0

Barman is finishing its move from a backup host to a cloud-native lifecycle.

◆ Current state

EnterpriseDB has spent the last four releases rebuilding Barman around object storage. 3.18.0 added block-level incremental backups direct to cloud with only a small staging area on the Barman host; 3.19.0 closed the loop with cloud restore and a dedicated cloud-wal-restore command. Encryption and compression restrictions on incremental backups were removed in 3.14/3.15, and the release notes are unusually detailed — each change carries a rationale and a BAR- ticket reference.

◆ Where it's heading

The Barman host is being demoted from storage tier to control plane. Every recent release moves another operation that required local disk into object storage, and the deprecations follow the same line — local_staging_path and recovery_staging_path replaced by a generic staging_path plus staging_location. The care taken over CloudNativePG compatibility in 3.16.1 shows Kubernetes-operator deployments are now a constituency worth issuing a point release for.

◆ Prediction

Expect the remaining barman-cloud-* standalone scripts to be folded into the main barman command surface, continuing the pattern set by cloud-wal-restore. Deprecated compression and staging options are the likely removals in the next major.

E5.0

Three OTP branches move as one release train, and SSH and epmd carry the security load.

◆ Current state

Erlang/OTP is patching three branches in lockstep — 29 as current, 28 and 27 as maintenance — with each fix set published as a trio within minutes of itself. The window is dominated by security work in the network-facing applications: OTP 29.0.4 carried six CVEs including an epmd denial-of-service mitigation, and the 4 August trio brought SSH into line with RFC 4253 by rejecting packets not aligned to the cipher block size, with a timing-safe packet-discard path for CBC ciphers. A regression in the previous patch that stopped epmd binding to localhost was fixed in the same trio.

◆ Where it's heading

The maintenance pattern is unusually strict: 27, 28 and 29 receive the same trouble reports on the same day, so the effective support window is wide and sites on older majors are not being pushed forward by security pressure. Where the fixes land is consistent — ssh, ssl, crypto, public_key and erts account for nearly every changed application across these releases, which is the distribution epmd and the TLS/SSH stack impose on a distributed runtime. The CBC timing mitigation in particular is an old class of attack being closed properly rather than papered over.

◆ Prediction

Expect the next patch trio to follow the same shape — a small set of trouble reports applied to all three branches simultaneously — with ssh and ssl the most likely applications to change. Nothing in these entries indicates feature work landing on the patch branches; that stays on the next major.

Alternatives to Barman and Erlang/OTP

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 Barman or Erlang/OTP.

See all Barman alternatives → · See all Erlang/OTP alternatives →

Recent activity from Barman and Erlang/OTP

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 5d agoErlang/OTPSSH now rejects misaligned packets with a timing-safe discard
  2. 5d agoErlang/OTPOTP 28 takes the same SSH alignment and epmd fixes
  3. 5d agoErlang/OTPOTP 27 receives the same erts and ssh patches
  4. 12d agoErlang/OTP27 July patch touches crypto, ssl, ssh and public_key on OTP 28
  5. 12d agoErlang/OTPOTP 27 mirrors the 27 July crypto and transport patch
  6. 12d agoErlang/OTPOTP 29.0.4 carries six CVEs and an epmd DoS mitigation
  7. 2mo agoBarmanFix cloud-wal-restore missing prefix-colliding WAL files
  8. 2mo agoBarmanCloud restore closes Barman's object-storage lifecycle
  9. 4mo agoBarmanBlock-level incremental backups land in cloud storage
  10. 7mo agoBarmanQuery and restore now work on inactive servers
  11. 9mo agoBarmanDetect MissingContentMD5 errors by message on S3-compatible stores
  12. 9mo agoBarmanBucket auto-creation returns for CloudNativePG compatibility

Frequently asked questions

What is the difference between Barman and Erlang/OTP?

They serve adjacent needs but don't currently overlap on shipped themes. Erlang/OTP is currently shipping more aggressively (velocity 5.0 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 Barman better than Erlang/OTP?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Erlang/OTP is currently shipping more aggressively (velocity 5.0 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 Barman?

Top Barman alternatives in DevOps are ranked by recent ship velocity. Browse the "Barman alternatives" section above for the current picks, or visit /alternatives/barman for the full list with editorial commentary on each.

What are the best alternatives to Erlang/OTP?

Top Erlang/OTP alternatives in DevOps are ranked by recent ship velocity. Browse the "Erlang/OTP alternatives" section above for the current picks, or visit /alternatives/erlang-otp for the full list with editorial commentary on each.