DBMS > EJDB vs. Galaxybase vs. IBM Db2 Event Store vs. Snowflake

System Properties Comparison EJDB vs. Galaxybase vs. IBM Db2 Event Store vs. Snowflake

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)

Scalable, ACID-compliant native distributed parallel graph platform

Distributed Event Store optimized for Internet of Things use cases

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Document store

Graph DBMS

Event Store
Time Series DBMS

Relational DBMS

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

Score	0.13
Rank	#331	Overall
	#46	Document stores

Score	0.00
Rank	#385	Overall
	#40	Graph DBMS

Score	0.18
Rank	#315	Overall
	#2	Event Stores
	#26	Time Series DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Website

github.com/Softmotions/ejdb

galaxybase.com

www.ibm.com/products/db2-event-store

www.snowflake.com

Technical documentation

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

www.ibm.com/docs/en/db2-event-store

docs.snowflake.net/manuals/index.html

Developer

Softmotions

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

IBM

Snowflake Computing Inc.

Initial release

2012

2017

2014

Current release

Nov 20, November 2021

2.0

License

Commercial or Open Source

Open Source

GPLv2

commercial

free developer edition available

commercial

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 and Java

C and C++

Server operating systems

server-less

Linux

Linux, macOS, Windows for the developer addition

hosted

Data scheme

schema-free

Strong typed schema

yes

support of semi-structured data formats (JSON, XML, Avro)

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

Secondary indexes

yes

SQL

Support of SQL

yes

through the embedded Spark runtime

yes

APIs and other access methods

in-process shared library

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

ADO.NET
DB2 Connect
JDBC
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

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

Go
Java
Python

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined procedures and functions

yes

user defined functions

Triggers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Active-active shard replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Relationships in graphs

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

No - written data is immutable

yes

Durability

Support for making data persistent

yes

Yes - Synchronous writes to local disk combined with replication and asynchronous writes in parquet format to permanent shared storage

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

Role-based access control

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept, user roles and pluggable authentication

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.