DBMS > EJDB vs. Manticore Search vs. TimesTen vs. Tkrzw

System Properties Comparison EJDB vs. Manticore Search vs. TimesTen vs. Tkrzw

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)

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

In-Memory RDBMS compatible to Oracle

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

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.22
Rank	#312	Overall
	#21	Search engines

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

github.com/Softmotions/ejdb

manticoresearch.com

www.oracle.com/database/technologies/related/timesten.html

dbmx.net/tkrzw

Technical documentation

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

manual.manticoresearch.com

docs.oracle.com/database/timesten-18.1

Developer

Softmotions

Manticore Software

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Mikio Hirabayashi

Initial release

2012

2017

1998

2020

Current release

6.0, February 2023

11 Release 2 (11.2.2.8.0)

0.9.3, August 2020

License

Commercial or Open Source

Open Source

GPLv2

Open Source

GPL version 2

commercial

Open Source

Apache Version 2.0

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

C++

Server operating systems

server-less

FreeBSD
Linux
macOS
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
macOS

Data scheme

schema-free

Fixed schema

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

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
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

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

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

C
C++
Java
PL/SQL

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

PL/SQL

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication based on Galera library

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

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

yes

by means of logfiles and checkpoints

yes

In-memory capabilities

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

yes

using specific database classes

User concepts

Access control

fine grained access rights according to SQL-standard

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

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

In-memory databases with Emulex Gen 7
25 October 2023, Broadcom Inc.

provided by Google News

Share this page