DBMS > Dragonfly vs. EJDB vs. Spark SQL vs. Transbase

System Properties Comparison Dragonfly vs. EJDB vs. Spark SQL vs. Transbase

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

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Key-value store

Document store

Relational DBMS

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

Score	0.42
Rank	#271	Overall
	#38	Key-value stores

Score	0.30
Rank	#294	Overall
	#44	Document stores

Score	19.15
Rank	#33	Overall
	#20	Relational DBMS

Score	0.15
Rank	#337	Overall
	#147	Relational DBMS

Website

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

github.com/Softmotions/ejdb

spark.apache.org/sql

www.transaction.de/en/products/transbase.html

Technical documentation

www.dragonflydb.io/docs

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

spark.apache.org/docs/latest/sql-programming-guide.html

www.transaction.de/en/products/transbase/features.html

Developer

DragonflyDB team and community contributors

Softmotions

Apache Software Foundation

Transaction Software GmbH

Initial release

2023

2012

2014

1987

Current release

1.0, March 2023

3.5.0 ( 2.13), September 2023

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

BSL 1.1

Open Source

GPLv2

Open Source

Apache 2.0

commercial

free development license

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++

Scala

C and C++

Server operating systems

Linux

server-less

Linux
OS X
Windows

FreeBSD
Linux
macOS
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

string, integer, double, bool, date, object_id

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

SQL

Support of SQL

SQL-like DML and DDL statements

yes

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

in-process shared library

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

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

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

Java
Python
R
Scala

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

Lua

yes

Triggers

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes, utilizing Spark Core

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

Atomic execution of command blocks and scripts

yes

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

yes

Read/Write Locking

yes

Durability

Support for making data persistent

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

Password-based authentication

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

DragonflyDB Announces $21m in New Funding and General Availability
21 March 2023, Business Wire

DragonflyDB reels in $21M for its speedy in-memory database
21 March 2023, SiliconANGLE News

DragonflyDB Raises $21M in Funding
21 March 2023, FinSMEs

Dragonfly 1.0 Released For What Claims To Be The World's Fastest In-Memory Data Store
20 March 2023, Phoronix

Intel Linux Kernel Optimizations Show Huge Benefit For High Core Count Servers
29 March 2023, Phoronix

provided by Google News

Use Amazon Athena with Spark SQL for your open-source transactional table formats | Amazon Web Services
24 January 2024, AWS Blog

What is Apache Spark? The big data platform that crushed Hadoop
3 April 2024, InfoWorld

Cracking the Apache Spark Interview: 80+ Top Questions and Answers for 2024
1 April 2024, Simplilearn

1.5 Years of Spark Knowledge in 8 Tips | by Michael Berk
23 December 2023, Towards Data Science

Run Apache Hive workloads using Spark SQL with Amazon EMR on EKS | Amazon Web Services
18 October 2023, AWS Blog

provided by Google News

Share this page