DBMS > EJDB vs. OrigoDB vs. SpatiaLite vs. Yanza

System Properties Comparison EJDB vs. OrigoDB vs. SpatiaLite vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

A fully ACID in-memory object graph database

Spatial extension of SQLite

Time Series DBMS for IoT Applications

Primary database model

Document store

Document store
Object oriented DBMS

Spatial DBMS

Time Series DBMS

Secondary database models

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	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Website

github.com/Softmotions/ejdb

origodb.com

www.gaia-gis.it/fossil/libspatialite/index

yanza.com

Technical documentation

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

origodb.com/docs

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Softmotions

Robert Friberg et al

Alessandro Furieri

Yanza

Initial release

2012

2009

under the name LiveDB

2008

2015

Current release

5.0.0, August 2020

License

Commercial or Open Source

Open Source

GPLv2

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Server operating systems

server-less

Linux
Windows

server-less

Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

in-process shared library

.NET Client API
HTTP API
LINQ

HTTP API

Supported programming languages

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

.Net

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

Triggers

yes

Domain Events

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

Role based authorization

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.