immudb
immudb made itself speak Postgres — while its announced v2 rearchitecture sits unfinished.
Comparison · DevOps
Manticore Search vs Vitess
A side-by-side editorial comparison of Manticore Search and Vitess — release velocity, themes, recent moves, and the top alternatives to consider.
Manticore Search vs Vitess: at a glance
What is Manticore Search?
Manticore tags a GitHub release per commit, so the real news is one entry in five.
Only one item in the recent window is a release in the ordinary sense: 28.6.6, whose notes cover UUID document IDs for real-time tables — explicit or generated, with equality and IN filters and UUID-based REPLACE, UPDATE and DELETE — and an ordered, limited GROUP_CONCAT() that keeps the top N values per group. The rest are individual commits published as releases: a buddy dependency bump, a backup component bump, a fix restoring USER() parsing after authentication made USER a keyword, and a revert of UTF-8 table and field name support that had been merged by mistake.
What is Vitess?
Two patch lines, every release published twice, and no feature news since v24.0.0.
The recent window is maintenance on two supported branches: v24.0.2 (34 merged pull requests) and v23.0.5 (35) in late June, preceded by v24.0.1 and v23.0.4 in May. None of these releases describe their contents — each body is a pull-request count and a contributor list, with the actual changelog behind a link. Every release also appears a second time as a `v0.x.y` Go-module tag carrying only a sign-off line.
Manticore Search vs Vitess: editorial side-by-side
Manticore Search
5.0DEVOPS
Manticore tags a GitHub release per commit, so the real news is one entry in five.
◆ Current state
Only one item in the recent window is a release in the ordinary sense: 28.6.6, whose notes cover UUID document IDs for real-time tables — explicit or generated, with equality and IN filters and UUID-based REPLACE, UPDATE and DELETE — and an ordered, limited GROUP_CONCAT() that keeps the top N values per group. The rest are individual commits published as releases: a buddy dependency bump, a backup component bump, a fix restoring USER() parsing after authentication made USER a keyword, and a revert of UTF-8 table and field name support that had been merged by mistake.
◆ Where it's heading
The feature direction visible here is making Manticore behave more like the SQL engine users expect. UUID identifiers remove the requirement to mint your own document IDs, the GROUP_CONCAT extension closes a gap against MySQL semantics, and the USER() fix is repairing MySQL client compatibility that the new authentication support broke. The reverted UTF-8 identifier support belongs to the same effort and will presumably return deliberately.
◆ Prediction
UTF-8 table and field names were reverted as merged by mistake rather than rejected, so the clearest next step is that feature landing properly. The commit-per-release pattern means most upcoming entries will continue to be single fixes rather than release notes.
Vitess
0.0DEVOPS
Two patch lines, every release published twice, and no feature news since v24.0.0.
◆ Current state
The recent window is maintenance on two supported branches: v24.0.2 (34 merged pull requests) and v23.0.5 (35) in late June, preceded by v24.0.1 and v23.0.4 in May. None of these releases describe their contents — each body is a pull-request count and a contributor list, with the actual changelog behind a link. Every release also appears a second time as a `v0.x.y` Go-module tag carrying only a sign-off line.
◆ Where it's heading
Feature work is concentrated in the majors, not the patches. v24.0.0 at the end of April was the substantive release: window function pushdown for sharded keyspaces, view routing rules, tablet targeting through USE statements, VTGate binlog streaming and structured logging, with external decompressors no longer read from the backup manifest by default. Since then the branches have been in pure upkeep.
◆ Prediction
On the pattern here — a major in April followed by monthly patches on both supported branches — the next thing to expect is continued v23.0.z and v24.0.z patches rather than new capability. The bodies give no indication of what a v25 would contain.
Alternatives to Manticore Search and Vitess
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 Manticore Search or Vitess.
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.
NebulaGraph
A graph database spending its releases on query-language parity and traversal speed.
pgBackRest
PostgreSQL 19 support lands, and pgBackRest stops letting you run most commands as root.
Heroku
Runtime bumps fill the changelog; the managed Postgres line is where Heroku actually moves.
See all Manticore Search alternatives → · See all Vitess alternatives →
Recent activity from Manticore Search and Vitess
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23h agoManticore SearchUTF-8 table and field name support reverted
- 1d agoManticore SearchBuddy component bumped from 4.2.0 to 4.3.0
- 7d agoManticore SearchUUID document IDs and ordered, limited GROUP_CONCAT()
- 8d agoManticore SearchUSER() parsing restored for MySQL client compatibility
- 9d agoManticore SearchBackup component bumped to 1.10.2
- 1mo agoVitessVitess v24.0.2 patch release (34 pull requests)
- 1mo agoVitessGo-module tag for the v24.0.2 release
- 1mo agoVitessVitess v23.0.5 patch release (35 pull requests)
- 1mo agoVitessGo-module tag for the v23.0.5 release
- 3mo agoVitessVitess v24.0.1 patch release (6 pull requests)
- 3mo agoVitessGo-module tag for the v24.0.1 release
Frequently asked questions
What is the difference between Manticore Search and Vitess?
They serve adjacent needs but don't currently overlap on shipped themes. Manticore Search 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 Manticore Search better than Vitess?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Manticore Search 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 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.
What are the best alternatives to Vitess?
Top Vitess alternatives in DevOps are ranked by recent ship velocity. Browse the "Vitess alternatives" section above for the current picks, or visit /alternatives/vitess for the full list with editorial commentary on each.