Dapr
Dapr is shipping fixes across three release branches at once, most of them in workflows.
Comparison · DevOps
GeoServer vs Manticore Search
A side-by-side editorial comparison of GeoServer and Manticore Search — release velocity, themes, recent moves, and the top alternatives to consider.
GeoServer vs Manticore Search: at a glance
What is GeoServer?
GeoServer patches three branches at once, with the new work reserved for the 3.0 line
Three releases landed within about an hour of each other — 2.27.6, 2.28.5 and 3.0.1 — the coordinated multi-branch pattern this project uses for maintenance. The shared payload is a set of security-adjacent fixes: a GeoFence SQL query missing its spatial filter when only CLIP applies, wrong CRS axis order when clipping WFS 2.0.0 features, and the XXE vulnerability in features-templating backported to the oldest branch. Only 3.0.1 carries new capability: a Keycloak role service and security-aware GeoWebCache tile caching.
What is Manticore Search?
Manticore's 29.0 line finally makes native sharded tables something you can operate, not just create
Manticore ships continuously through version-tagged commits punctuated by consolidated release notes, and 29.0.2 is the first of those since 28.6.6. The through-line is sharding: sharded tables gained settings inspection, synchronous OPTIMIZE across distributed and sharded components, and a changed SHARD_WRITE protocol that streams heartbeat replies during long writes and replication SST. Around it sit columnar and KNN performance work, configurable file access modes, and a steady stream of fixes to backups, highlighting, JDBC compatibility and RT-table optimization.
GeoServer vs Manticore Search: editorial side-by-side
GeoServer
5.0DEVOPS
GeoServer patches three branches at once, with the new work reserved for the 3.0 line
◆ Current state
Three releases landed within about an hour of each other — 2.27.6, 2.28.5 and 3.0.1 — the coordinated multi-branch pattern this project uses for maintenance. The shared payload is a set of security-adjacent fixes: a GeoFence SQL query missing its spatial filter when only CLIP applies, wrong CRS axis order when clipping WFS 2.0.0 features, and the XXE vulnerability in features-templating backported to the oldest branch. Only 3.0.1 carries new capability: a Keycloak role service and security-aware GeoWebCache tile caching.
◆ Where it's heading
The branch split is doing what it is supposed to. The 2.x lines get fixes and nothing else, while the 3.0 line — which broke the monolith into extensions — is where authentication and cache-security work now lands. The recurring theme across all three is access control at the data layer: GeoFence filtering, secured feature sources, and now tile caching that respects security rather than serving from an unaware cache.
◆ Prediction
Expect the next coordinated round to follow the same shape, with 3.0.2 taking further security-aware caching and identity-provider work while the 2.x branches receive only the shared fixes.
Manticore Search
6.3DEVOPS
Manticore's 29.0 line finally makes native sharded tables something you can operate, not just create
◆ Current state
Manticore ships continuously through version-tagged commits punctuated by consolidated release notes, and 29.0.2 is the first of those since 28.6.6. The through-line is sharding: sharded tables gained settings inspection, synchronous OPTIMIZE across distributed and sharded components, and a changed SHARD_WRITE protocol that streams heartbeat replies during long writes and replication SST. Around it sit columnar and KNN performance work, configurable file access modes, and a steady stream of fixes to backups, highlighting, JDBC compatibility and RT-table optimization.
◆ Where it's heading
The engine is closing the gap between having native sharding and being able to run it — the last three releases have each handed operators a control that previously only existed for single local tables. Search-side work is bifurcating between classic full-text concerns (snippets, boolean simplification) and vector/AI paths: batched distance calculations in columnar KNN rescoring, and Buddy retrying failed LLM route-selection calls in conversational search. The revert of UTF-8 table names shows the release train is fast enough that things occasionally land before they are ready.
◆ Prediction
Expect the remaining single-table operational commands to be extended to sharded tables next, and the conversational search path to keep hardening now that it depends on an external LLM call. Whether UTF-8 identifiers return in the 29.x line is unclear from these entries.
Alternatives to GeoServer and Manticore Search
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 GeoServer or Manticore Search.
rtoot
rtoot reached 1.0 by rebuilding on httr2 rather than by adding anything new.
ipumsr
ipumsr is collapsing a dozen collection-specific APIs into one extract vocabulary.
collections
A stable R data-structure package whose releases are now mostly compiler and checker upkeep.
Z-Wave JS UI
Z-Wave JS UI is hardening its network surface while handing issue triage to agents.
gtfsio
gtfsio's job is absorbing the ways real transit feeds violate their own specification.
See all GeoServer alternatives → · See all Manticore Search alternatives →
Recent activity from GeoServer and Manticore Search
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 19h agoGeoServer2.27.6 backports the XXE fix and workspace style persistence
- 19h agoGeoServer2.28.5 fixes GeoFence spatial filtering and WFS clipping axis order
- 20h agoGeoServer3.0.1 adds a Keycloak role service and security-aware tile caching
- 1d agoManticore SearchManticore 29.0 makes sharded tables operable and changes the SHARD_WRITE protocol ⚡
- 1d agoManticore Search29.0.2 bumps manticore-backup to 1.10.3 and Buddy to 4.4.1
- 3d agoManticore SearchSHOW TABLE SETTINGS now works on sharded tables
- 4d agoManticore SearchSnippet highlighting preserves nested markup
- 4d agoManticore SearchFixes one case of the thread stack error
- 5d agoManticore SearchPer-index optimize_cutoff now applies to KNN too
- 2mo agoGeoServerGeoServer 3.0 splits the core into extensions and drops H2 ⚡
- 2mo agoGeoServer2.28.4 fixes an XXE vulnerability and adds per-version service toggles
- 5mo agoGeoServer2.28.2 adds STAC security and REST ingestion for VectorMosaic
Frequently asked questions
What is the difference between GeoServer and Manticore Search?
They serve adjacent needs but don't currently overlap on shipped themes. Manticore Search is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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 GeoServer better than Manticore Search?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Manticore Search is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 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 GeoServer?
Top GeoServer alternatives in DevOps are ranked by recent ship velocity. Browse the "GeoServer alternatives" section above for the current picks, or visit /alternatives/geoserver for the full list with editorial commentary on each.
What are the best alternatives to Manticore Search?
Top Manticore Search alternatives in DevOps are ranked by recent ship velocity. Browse the "Manticore Search alternatives" section above for the current picks, or visit /alternatives/manticoresearch for the full list with editorial commentary on each.