DBMS > EJDB vs. Microsoft SQL Server vs. Qdrant vs. SingleStore

System Properties Comparison EJDB vs. Microsoft SQL Server vs. Qdrant vs. SingleStore

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Microsofts flagship relational DBMS

A high-performance vector database with neural network or semantic-based matching

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Score	5.60
Rank	#62	Overall
	#35	Relational DBMS

Website

github.com/Softmotions/ejdb

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

github.com/qdrant/qdrant
qdrant.tech

www.singlestore.com

Technical documentation

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

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

qdrant.tech/documentation

docs.singlestore.com

Developer

Softmotions

Microsoft

Qdrant

SingleStore Inc.

Initial release

2012

1989

2021

2013

Current release

SQL Server 2022, November 2022

8.5, January 2024

License

Commercial or Open Source

Open Source

GPLv2

commercial

restricted free version is available

Open Source

Apache Version 2.0

commercial

free developer edition available

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.

SingleStoreDB Cloud: The world's fastest, modern cloud database for both operational (OLTP) and analytical (OLAP) workloads. Available instantly with multi-cloud and hybrid-cloud capabilities

Implementation language

C++

Rust

C++, Go

Server operating systems

server-less

Linux
Windows

Docker
Linux
macOS
Windows

Linux

64 bit version required

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

Numbers, Strings, Geo, Boolean

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

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

yes

but no triggers and foreign keys

APIs and other access methods

in-process shared library

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

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

Supported programming languages

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

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

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

Bash
C
C#
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

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

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

Sharding

hash partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes, but depending on the SQL-Server Edition

Collection-level replication

Source-replica replication

stores two copies of each physical data partition on two separate nodes

MapReduce

Offers an API for user-defined Map/Reduce methods

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency, tunable 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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

In-memory capabilities

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Key-based authentication

Fine grained access control via users, groups and roles

More information provided by the system vendor

Specific characteristics

SingleStore offers a fully-managed , distributed, highly-scalable SQL database designed...
» more

Competitive advantages

SingleStore’s competitive advantages include: Easy and Simplified Architecture with...
» more

Typical application scenarios

Driving Fast Analytics: SingleStore delivers the fastest and most scalable reporting...
» more

Key customers

IEX Cloud : Improves Financial Data Distribution Speed 15x with Singlestore DB Comcast,...
» more

Market metrics

Customers in various industries worldwide including US and International Industry...
» more

Licensing and pricing models

F ree Tier and Enterprise Edition
» 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.