DBMS > Dragonfly vs. Ehcache vs. Google BigQuery vs. Sphinx

System Properties Comparison Dragonfly vs. Ehcache vs. Google BigQuery vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A drop-in Redis replacement that scales vertically to support millions of operations per second and terabyte sized workloads, all on a single instance

A widely adopted Java cache with tiered storage options

Large scale data warehouse service with append-only tables

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Key-value store

Relational DBMS

Search engine

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

Score	0.41
Rank	#266	Overall
	#38	Key-value stores

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

github.com/dragonflydb/dragonfly
www.dragonflydb.io

www.ehcache.org

cloud.google.com/bigquery

sphinxsearch.com

Technical documentation

www.dragonflydb.io/docs

www.ehcache.org/documentation

cloud.google.com/bigquery/docs

sphinxsearch.com/docs

Developer

DragonflyDB team and community contributors

Terracotta Inc, owned by Software AG

Google

Sphinx Technologies Inc.

Initial release

2023

2009

2010

2001

Current release

1.0, March 2023

3.10.0, March 2022

3.5.1, February 2023

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

GPL version 2, commercial licence 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

C++

Java

C++

Server operating systems

Linux

All OS with a Java VM

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

scheme-free

schema-free

yes

Typing

predefined data types such as float or date

strings, hashes, lists, sets, sorted sets, bit arrays

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.

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

JCache

RESTful HTTP/JSON API

Proprietary protocol

Supported programming languages

C
C#
C++
Clojure
D
Dart
Elixir
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
Objective-C
Perl
PHP
Python
R
Ruby
Rust
Scala
Swift
Tcl

Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

Lua

user defined functions

in JavaScript

Triggers

publish/subscribe channels provide some trigger functionality

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

none

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

by using Terracotta Server

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of command blocks and scripts

yes

supports JTA and can work as an XA resource

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

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

In-memory capabilities

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

yes

User concepts

Access control

Password-based authentication

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.