DBMS > EJDB vs. FatDB vs. OrigoDB vs. SAP SQL Anywhere vs. Snowflake

System Properties Comparison EJDB vs. FatDB vs. OrigoDB vs. SAP SQL Anywhere vs. Snowflake

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

A fully ACID in-memory object graph database

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

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

Primary database model

Document store

Document store
Key-value store

Document store
Object oriented DBMS

Relational DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	3.95
Rank	#80	Overall
	#42	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

github.com/Softmotions/ejdb

origodb.com

www.sap.com/products/technology-platform/sql-anywhere.html

www.snowflake.com

Technical documentation

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

origodb.com/docs

help.sap.com/docs/SAP_SQL_Anywhere

docs.snowflake.net/manuals/index.html

Developer

Softmotions

FatCloud

Robert Friberg et al

SAP

formerly Sybase

Snowflake Computing Inc.

Initial release

2012

2009

under the name LiveDB

1992

2014

Current release

17, July 2015

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

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

Server operating systems

server-less

Windows

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

hosted

Data scheme

schema-free

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

User defined using .NET types and collections

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.

can be achieved using .NET

yes

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

APIs and other access methods

in-process shared library

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

.NET Client API
HTTP API
LINQ

ADO.NET
HTTP API
JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

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

.Net

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

via applications

yes

yes, in C/C++, Java, .Net or Perl

user defined functions

Triggers

yes

via applications

yes

Domain Events

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

client side managed; servers are not synchronized

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

Source-replica replication

Database mirroring

yes

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

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

depending on model

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

Durability

Support for making data persistent

yes

Write ahead log

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

Can implement custom security layer via applications

Role based authorization

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.