DBMS > EJDB vs. Heroic vs. Lovefield vs. Manticore Search

System Properties Comparison EJDB vs. Heroic vs. Lovefield vs. Manticore Search

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Embeddable relational database for web apps written in pure JavaScript

Multi-storage database for search, including full-text search.

Primary database model

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	0.22
Rank	#312	Overall
	#21	Search engines

Website

github.com/Softmotions/ejdb

github.com/spotify/heroic

google.github.io/lovefield

manticoresearch.com

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

spotify.github.io/heroic

github.com/google/lovefield/blob/master/docs/spec_index.md

manual.manticoresearch.com

Developer

Softmotions

Spotify

Google

Manticore Software

Initial release

2012

2014

2017

Current release

2.1.12, February 2017

6.0, February 2023

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

GPL version 2

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

JavaScript

C++

Server operating systems

server-less

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

FreeBSD
Linux
macOS
Windows

Data scheme

schema-free

yes

Fixed schema

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

Can index from XML

Secondary indexes

yes

via Elasticsearch

yes

full-text index on all search fields

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

SQL-like query language

APIs and other access methods

in-process shared library

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

JavaScript

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

none

Synchronous replication based on Galera library

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

yes

isolated transactions for atomic changes and binary logging for safe writes

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

The original contents of fields are not stored in the Manticore index.

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

User concepts

Access control

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

provided by Google News

Integrating Manticore Search with Apache Superset
8 August 2023, hackernoon.com

Clickhouse vs Elasticsearch vs Manticore Search Query Times With a 1.7B NYC Taxi Rides Benchmark
1 June 2022, hackernoon.com

Google's Gemini comes to databases
9 April 2024, Yahoo Canada Shine On

Comparing Meilisearch and Manticore Search Using Key Benchmarks
2 May 2023, hackernoon.com

8 Google Alternatives: How to Search Crypto, the Dark Web, More
1 February 2023, Gizmodo

provided by Google News

Share this page