DBMS > Ehcache vs. Manticore Search vs. ScyllaDB vs. SQLite

System Properties Comparison Ehcache vs. Manticore Search vs. ScyllaDB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

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

Cassandra and DynamoDB compatible wide column store

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Key-value store

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

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	4.08
Rank	#76	Overall
	#5	Wide column stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

www.ehcache.org/documentation

manual.manticoresearch.com

docs.scylladb.com

www.sqlite.org/docs.html

Developer

Terracotta Inc, owned by Software AG

Manticore Software

ScyllaDB

Dwayne Richard Hipp

Initial release

2009

2017

2015

2000

Current release

3.10.0, March 2022

6.0, February 2023

ScyllaDB Open Source 5.4.1, January 2024

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL version 2

Open Source

Open Source (AGPL), commercial license available

Open Source

Public Domain

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.

Scylla Cloud: Create real-time applications that run at global scale with Scylla Cloud, the industry’s most powerful NoSQL DBaaS

Implementation language

Java

C++

Server operating systems

All OS with a Java VM

FreeBSD
Linux
macOS
Windows

Linux

server-less

Data scheme

schema-free

Fixed schema

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

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

yes

not rigid because of 'dynamic typing' concept.

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

cluster global secondary indices

yes

SQL

Support of SQL

SQL-like query language

SQL-like DML and DDL statements (CQL)

yes

SQL-92 is not fully supported

APIs and other access methods

JCache

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

Proprietary protocol (CQL)

compatible with CQL (Cassandra Query Language, an SQL-like language)
RESTful HTTP API (DynamoDB compatible)
Thrift

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java

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

For CQL interface: C#, C++, Clojure, Erlang, Go, Haskell, Java, JavaScript, Node.js, Perl, PHP, Python, Ruby, Rust, Scala
For DynamoDB interface: .Net, ColdFusion, Erlang, Groovy, Java, JavaScript, Perl, PHP, Python, Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

yes, Lua

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Synchronous replication based on Galera library

selectable replication factor

Representation of geographical distribution of servers is possible

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency
Tunable Consistency

can be individually decided for each write operation

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

supports JTA and can work as an XA resource

yes

isolated transactions for atomic changes and binary logging for safe writes

Atomicity and isolation are supported for single operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

in-memory tables

yes

User concepts

Access control

Access rights for users can be defined per object

More information provided by the system vendor

Specific characteristics

ScyllaDB is engineered to deliver predictable performance at scale. It’s adopted...
» more

Competitive advantages

Highly-performant (efficiently utilizes full resources of a node and network; millions...
» more

Typical application scenarios

ScyllaDB is ideal for applications that require high throughput and low latency at...
» more

Key customers

Discord, Epic Games, Expedia, Zillow, Comcast, Disney+ Hotstar, Samsung, ShareChat,...
» more

Market metrics

ScyllaDB typically offers ~75% total cost of ownership savings, with ~5X higher throughput...
» more

Licensing and pricing models

ScyllaDB Open Source - free open source software (AGPL) ScyllaDB Enterprise - subscription-based...
» more

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.