← Back to home
Comparison · DevOps

Apollo Config vs Erlang/OTP

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

Apollo Config vs Erlang/OTP: at a glance

FeatureApollo ConfigErlang/OTP
SectorDevOpsDevOps
Velocity score2.55.0
Sparks · 30d00
Top themesconfig-management, operational-cost, permissions, incremental-syncruntime, security, ssh, tls
Last editorial update3h ago4h ago
WebsiteVisit →Visit →

What is Apollo Config?

Apollo is grinding down the operational cost of running a config service.

Apollo ships a feature release roughly once a year with small patches between them. The 2.5 line added incremental configuration synchronisation, where Config Service caches release state and returns only changed items behind an opt-in flag, plus app-level config export and import with ignore or cover conflict handling, and self-service profile updates for non-admin users. The two patches since were both permission and authentication corrections: super admin inclusion in unified permission checks, and AccessKey app ID validation during client authentication.

Read the full Apollo Config 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 →

Apollo Config vs Erlang/OTP: editorial side-by-side

A2.5

Apollo is grinding down the operational cost of running a config service.

◆ Current state

Apollo ships a feature release roughly once a year with small patches between them. The 2.5 line added incremental configuration synchronisation, where Config Service caches release state and returns only changed items behind an opt-in flag, plus app-level config export and import with ignore or cover conflict handling, and self-service profile updates for non-admin users. The two patches since were both permission and authentication corrections: super admin inclusion in unified permission checks, and AccessKey app ID validation during client authentication.

◆ Where it's heading

Each feature release removes a specific piece of operational friction. 2.3.0 made the whole server system start in one process without MySQL; 2.4.0 added global key and value search, observer mode for AccessKeys before enforcement, and namespace and item count limits; 2.5.0 cut the network cost of config polling and made bulk migration possible. The pattern is a mature system being made cheaper to run and safer to change, not one chasing new capability.

◆ Prediction

Incremental sync shipped behind a flag requiring a restart, so the next step is likely making it the default once field data supports it.

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

See all Apollo Config alternatives → · See all Erlang/OTP alternatives →

Recent activity from Apollo Config 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. 13d agoErlang/OTP27 July patch touches crypto, ssl, ssh and public_key on OTP 28
  5. 13d agoErlang/OTPOTP 27 mirrors the 27 July crypto and transport patch
  6. 13d agoErlang/OTPOTP 29.0.4 carries six CVEs and an epmd DoS mitigation
  7. 28d agoApollo ConfigAccessKey app ID validation during client authentication
  8. 4mo agoApollo ConfigSuper admin included in unified permission checks
  9. 5mo agoApollo ConfigIncremental config sync, app-level export and import
  10. 1y agoApollo ConfigGlobal key and value search, AccessKey observer mode, namespace limits
  11. 1y agoApollo ConfigWhole server system starts in a single process without MySQL
  12. 2y agoApollo ConfigTyped config items, admin list views, database as service registry

Frequently asked questions

What is the difference between Apollo Config 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 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 Apollo Config 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 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 Apollo Config?

Top Apollo Config alternatives in DevOps are ranked by recent ship velocity. Browse the "Apollo Config alternatives" section above for the current picks, or visit /alternatives/apollo-config 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.