DBMS > Dragonfly vs. EsgynDB vs. Microsoft SQL Server vs. mSQL vs. SpaceTime

System Properties Comparison Dragonfly vs. EsgynDB vs. Microsoft SQL Server vs. mSQL vs. SpaceTime

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

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Microsofts flagship relational DBMS

mSQL (Mini SQL) is a simple and lightweight RDBMS

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Key-value store

Relational DBMS

Spatial DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Relational DBMS

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

Score	0.49
Rank	#261	Overall
	#38	Key-value stores

Score	0.25
Rank	#312	Overall
	#138	Relational DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	1.27
Rank	#169	Overall
	#76	Relational DBMS

Score	0.03
Rank	#392	Overall
	#8	Spatial DBMS

Website

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

www.esgyn.cn

www.microsoft.com/en-us/sql-server

hughestech.com.au/products/msql

www.mireo.com/spacetime

Technical documentation

www.dragonflydb.io/docs

learn.microsoft.com/en-US/sql/sql-server

Developer

DragonflyDB team and community contributors

Esgyn

Microsoft

Hughes Technologies

Mireo

Initial release

2023

2015

1989

1994

2020

Current release

1.0, March 2023

SQL Server 2022, November 2022

4.4, October 2021

License

Commercial or Open Source

Open Source

BSL 1.1

commercial

restricted free version is available

commercial

free licenses can be provided

commercial

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

C++

C++, Java

C++

Server operating systems

Linux

Linux
Windows

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

Linux

Data scheme

scheme-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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

A subset of ANSI SQL is implemented

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protocol

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

JDBC
ODBC

RESTful HTTP 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

All languages supporting JDBC/ODBC/ADO.Net

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

C
C++
Delphi
Java
Perl
PHP
Tcl

C#
C++
Python

Server-side scripts

Stored procedures

Lua

Java Stored Procedures

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

publish/subscribe channels provide some trigger functionality

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication between multi datacenters

yes, but depending on the SQL-Server Edition

none

Real-time block device replication (DRBD)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of command blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes, strict serializability by the server

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

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.