DBMS > EJDB vs. Lovefield vs. Manticore Search vs. SAP HANA vs. searchxml

System Properties Comparison EJDB vs. Lovefield vs. Manticore Search vs. SAP HANA vs. searchxml

Editorial information provided by DB-Engines

Name

Description

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

Embeddable relational database for web apps written in pure JavaScript

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

In-memory, column based data store. Available as appliance or cloud service

DBMS for structured and unstructured content wrapped with an application server

Primary database model

Native XML DBMS
Search engine

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

github.com/Softmotions/ejdb

google.github.io/lovefield

manticoresearch.com

www.sap.com/products/hana.html

www.searchxml.net/category/products

Technical documentation

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

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

manual.manticoresearch.com

help.sap.com/hana

www.searchxml.net/support/handouts

Developer

Softmotions

Google

Manticore Software

SAP

informationpartners gmbh

Initial release

2012

2014

2017

2010

2015

Current release

2.1.12, February 2017

6.0, February 2023

2.0 SPS07 (April 4, 2023), April 2023

1.0

License

Commercial or Open Source

Open Source

GPLv2

Open Source

Apache 2.0

Open Source

GPL version 2

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

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

Appliance or cloud-service

Windows

Data scheme

schema-free

yes

Fixed schema

yes

schema-free

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

yes

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

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

SQL-like query language

yes

APIs and other access methods

in-process shared library

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

JDBC
ODBC

RESTful HTTP API
WebDAV
XQuery
XSLT

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

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

user defined functions

SQLScript, R

yes

on the application server

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication based on Galera library

yes

sychronisation to multiple collections

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

ACID

multiple readers, single writer

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.

yes

In-memory capabilities

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

yes

using MemoryDB

yes

User concepts

Access control

yes

Domain, group and role-based access control at the document level and for application services

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.