DBMS > AgensGraph vs. Atos Standard Common Repository vs. EJDB vs. Fauna vs. Snowflake

System Properties Comparison AgensGraph vs. Atos Standard Common Repository vs. EJDB vs. Fauna vs. Snowflake

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

Fauna provides a web-native interface, with support for GraphQL and custom business logic that integrates seamlessly with the rest of the serverless ecosystem. The underlying globally distributed storage and compute platform is fast, consistent, and reliable, with a modern security infrastructure.

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

Primary database model

Graph DBMS
Relational DBMS

Document store
Key-value store

Document store

Document store
Graph DBMS
Relational DBMS
Time Series DBMS

Relational DBMS

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

Score	0.23
Rank	#315	Overall
	#26	Graph DBMS
	#140	Relational DBMS

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	1.55
Rank	#151	Overall
	#26	Document stores
	#14	Graph DBMS
	#71	Relational DBMS
	#13	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

bitnine.net/agensgraph

atos.net/en/convergence-creators/portfolio/standard-common-repository

github.com/Softmotions/ejdb

fauna.com

www.snowflake.com

Technical documentation

bitnine.net/documentation

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

docs.fauna.com

docs.snowflake.net/manuals/index.html

Developer

Bitnine Global Inc.

Atos Convergence Creators

Softmotions

Fauna, Inc.

Snowflake Computing Inc.

Initial release

2016

2012

2014

Current release

2.1, December 2018

1703

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

GPLv2

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

Java

Scala

Server operating systems

Linux
OS X
Windows

Linux

server-less

hosted

Data scheme

depending on used data model

Schema and schema-less with LDAP views

schema-free

yes

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

Typing

predefined data types such as float or date

yes

optional

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

APIs and other access methods

Cypher Query Language
JDBC

LDAP

in-process shared library

RESTful HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

C
Java
JavaScript
Python

All languages with LDAP bindings

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

C#
Go
Java
JavaScript
Python
Ruby
Scala
Swift

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

cell division

none

horizontal partitioning

consistent hashing

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

none

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

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

Atomic execution of specific operations

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

LDAP bind authentication

Identity management, authentication, and access control

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.