Firebird
Firebird maintains three release branches at once and ships the same fixes to all of them
Comparison · DevOps
Nominatim vs Aerospike
A side-by-side editorial comparison of Nominatim and Aerospike — release velocity, themes, recent moves, and the top alternatives to consider.
Nominatim vs Aerospike: at a glance
What is Nominatim?
The geocoder finished becoming a Python package, then got back to matching addresses
Nominatim releases a minor version every few months with fast hotfixes when an update path breaks. The 4.5-to-5.0 span was structural — becoming a pip-installable Python package, then removing the PHP frontend, bundled osm2pgsql and cmake scripts outright. Since then the work has returned to geocoding quality: a pattern-based postcode parser, building entrances in results, a restructured forward query parser, and separate processing tables for postcodes, interpolations and associatedStreet relations.
What is Aerospike?
Aerospike shipped a coordinated CVE train across four release branches in one afternoon
On 16 July Aerospike published seven releases in under two hours, spanning the 7.1, 7.2, 8.0 and 8.1 branches, all carrying the same two waves of security fixes. The first wave — path traversal in UDF filename handling, an integer overflow in the msgpack size calculator, and a heap buffer overflow from missing op-size validation in batch writes — came with three numbered security bulletins. The second wave covered an out-of-bounds read in msgpack integer comparison, a memory leak on malformed proxy requests, and filter expressions bypassing validation on list and map values.
Nominatim vs Aerospike: editorial side-by-side
Nominatim
0.0DEVOPS
The geocoder finished becoming a Python package, then got back to matching addresses
◆ Current state
Nominatim releases a minor version every few months with fast hotfixes when an update path breaks. The 4.5-to-5.0 span was structural — becoming a pip-installable Python package, then removing the PHP frontend, bundled osm2pgsql and cmake scripts outright. Since then the work has returned to geocoding quality: a pattern-based postcode parser, building entrances in results, a restructured forward query parser, and separate processing tables for postcodes, interpolations and associatedStreet relations.
◆ Where it's heading
With the packaging migration finished, the project is optimizing the two things operators actually feel — how fast a search resolves and whether continuous OSM updates keep flowing. The 5.3.0 split into dedicated processing tables was explicitly about making updates faster and more reliable, and the two hotfixes that followed within a fortnight show how tightly that path is watched. Query-side work is trending toward recognizing input that is not in the database at all, as the postcode parser does.
◆ Prediction
Expect continued query-parser and update-pipeline optimization rather than new output types, since that is where every release since 5.0.0 has concentrated.
Aerospike
5.0DEVOPS
Aerospike shipped a coordinated CVE train across four release branches in one afternoon
◆ Current state
On 16 July Aerospike published seven releases in under two hours, spanning the 7.1, 7.2, 8.0 and 8.1 branches, all carrying the same two waves of security fixes. The first wave — path traversal in UDF filename handling, an integer overflow in the msgpack size calculator, and a heap buffer overflow from missing op-size validation in batch writes — came with three numbered security bulletins. The second wave covered an out-of-bounds read in msgpack integer comparison, a memory leak on malformed proxy requests, and filter expressions bypassing validation on list and map values.
◆ Where it's heading
The pattern is a vendor with long-lived enterprise deployments treating branch parity as a hard requirement: every fix is labelled with the editions it affects, and Community Edition receives the same security content as Enterprise and Federal. Most of the disclosed issues sit in msgpack parsing and collection data types, which is where untrusted client input first meets the server — a concentration that suggests a focused audit of that boundary rather than scattered reports. Outside the security work, releases are small: log verbosity, lock contention on cold-start eviction, transaction object-count accuracy.
◆ Prediction
Several CVEs in this train are still marked pending assignment, so expect follow-up releases as those are published and any related parsing paths are closed out. The branch-parity discipline shown here makes it likely that whatever lands next will again ship simultaneously across all four supported lines.
Alternatives to Nominatim and Aerospike
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 Nominatim or Aerospike.
GeoTools
GeoTools is migrating off dead Java imaging infrastructure that the whole GeoServer stack sits on
SU2
SU2 is growing from an aerodynamics solver into a coupled multiphysics optimizer
Psi4
Psi4 is closing the gap with ORCA on the methods that decide which code a lab installs
libosmium
libosmium is a stable OSM parsing library whose main work now is shedding old dependencies
OpenMM
OpenMM keeps opening new simulation domains while pushing more of the run onto the GPU
See all Nominatim alternatives → · See all Aerospike alternatives →
Recent activity from Nominatim and Aerospike
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 24d agoAerospikeAerospike 8.1.2.2 fixes UDF path traversal and batch heap overflow
- 24d agoAerospikeAerospike 8.1.2.3 fixes filter-expression validation bypass
- 24d agoAerospikeAerospike 8.0.0.18 backports the msgpack and proxy-leak fixes
- 24d agoAerospikeAerospike 8.0.0.17 backports the UDF and batch-write CVEs
- 25d agoAerospikeAerospike 7.2.0.20 backports second-wave fixes to the 7.2 branch
- 25d agoAerospikeAerospike 7.2.0.19 backports the UDF path traversal fix
- 3mo agoNominatim5.3.2 fixes a non-null constraint error during updates
- 4mo agoNominatim5.3.1 restores usable update speed for associatedStreet relations
- 4mo agoNominatim5.3.0 gives postcodes and interpolations their own processing tables
- 9mo agoNominatim5.2.0 returns building entrances and cuts SQL round-trips
- 1y agoNominatim5.1.0 recognizes postcodes that aren't in the OSM data
- 1y agoNominatim5.0.0 removes the PHP frontend, bundled osm2pgsql and cmake
Frequently asked questions
What is the difference between Nominatim and Aerospike?
They serve adjacent needs but don't currently overlap on shipped themes. Aerospike 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 Nominatim better than Aerospike?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Aerospike 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 Nominatim?
Top Nominatim alternatives in DevOps are ranked by recent ship velocity. Browse the "Nominatim alternatives" section above for the current picks, or visit /alternatives/nominatim for the full list with editorial commentary on each.
What are the best alternatives to Aerospike?
Top Aerospike alternatives in DevOps are ranked by recent ship velocity. Browse the "Aerospike alternatives" section above for the current picks, or visit /alternatives/aerospike for the full list with editorial commentary on each.