DBMS > Ehcache vs. Prometheus vs. Snowflake vs. Solr vs. TerarkDB

System Properties Comparison Ehcache vs. Prometheus vs. Snowflake vs. Solr vs. TerarkDB

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

Open-source Time Series DBMS and monitoring system

Cloud-based data warehousing service for structured and semi-structured data

A widely used distributed, scalable search engine based on Apache Lucene

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Secondary database models

Spatial DBMS

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

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

Score	7.69
Rank	#50	Overall
	#3	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	41.02
Rank	#24	Overall
	#3	Search engines

Score	0.08
Rank	#367	Overall
	#56	Key-value stores

Website

github.com/bytedance/terarkdb

Technical documentation

www.ehcache.org/documentation

prometheus.io/docs

docs.snowflake.net/manuals/index.html

solr.apache.org/resources.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Terracotta Inc, owned by Software AG

Snowflake Computing Inc.

Apache Software Foundation

ByteDance, originally Terark

Initial release

2009

2015

2014

2006

2016

Current release

3.10.0, March 2022

9.6.1, May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2

commercial

restricted open source version available

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C++

Server operating systems

All OS with a Java VM

Linux
Windows

hosted

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Dynamic Fields enables on-the-fly addition of new fields

schema-free

Typing

predefined data types such as float or date

yes

Numeric data only

yes

supports customizable data types and automatic typing

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.

Import of XML data possible

yes

Secondary indexes

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

Solr Parallel SQL Interface

APIs and other access methods

JCache

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Java API
RESTful HTTP/JSON API

C++ API
Java API

Supported programming languages

Java

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

JavaScript (Node.js)
Python

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

C++
Java

Server-side scripts

Stored procedures

user defined functions

Java plugins

Triggers

yes

Cache Event Listeners

similar concept for controling cloud resources

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

yes

by Federation

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

none

Immediate Consistency

Eventual Consistency

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

ACID

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

In-memory capabilities

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

yes

User concepts

Access control

Users with fine-grained authorization concept, user roles and pluggable authentication

yes

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.