DBMS > Badger vs. EJDB vs. Greenplum vs. Hazelcast vs. Microsoft SQL Server

System Properties Comparison Badger vs. EJDB vs. Greenplum vs. Hazelcast vs. Microsoft SQL Server

Editorial information provided by DB-Engines

Name

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

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

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

A widely adopted in-memory data grid

Microsofts flagship relational DBMS

Primary database model

Secondary database models

Document store
Spatial DBMS

Document store

JSON support with IMDG 3.12

Document store
Graph DBMS
Spatial DBMS

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

Score	0.20
Rank	#325	Overall
	#49	Key-value stores

Score	0.30
Rank	#294	Overall
	#44	Document stores

Score	9.23
Rank	#47	Overall
	#30	Relational DBMS

Score	6.87
Rank	#55	Overall
	#6	Key-value stores

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Website

github.com/dgraph-io/badger

github.com/Softmotions/ejdb

greenplum.org

hazelcast.com

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

Technical documentation

godoc.org/github.com/dgraph-io/badger

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

docs.greenplum.org

hazelcast.org/imdg/docs

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

Developer

DGraph Labs

Softmotions

Pivotal Software Inc.

Hazelcast

Microsoft

Initial release

2017

2012

2005

2008

1989

Current release

7.0.0, September 2023

5.3.6, November 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPLv2

Open Source

Apache 2.0

Open Source

Apache Version 2; commercial licenses available

commercial

restricted free version is 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.

Implementation language

Java

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

server-less

Linux

All OS with a Java VM

Linux
Windows

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

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

since Version 4.2

yes

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

in-process shared library

JDBC
ODBC

JCache
JPA
Memcached protocol
RESTful HTTP API

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

Supported programming languages

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

C
Java
Perl
Python
R

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

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

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

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

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

Replicated Map

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

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

one or two-phase-commit; repeatable reads; read commited

ACID

Concurrency

Support for concurrent manipulation of data

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

fine grained access rights according to SQL-standard

Role-based access control

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.