DBMS > DataFS vs. EJDB vs. Newts vs. SiteWhere vs. Yanza

System Properties Comparison DataFS vs. EJDB vs. Newts vs. SiteWhere vs. Yanza

Editorial information provided by DB-Engines

Name

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

Description

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

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

Time Series DBMS based on Cassandra

M2M integration platform for persisting/querying time series data

Time Series DBMS for IoT Applications

Primary database model

Object oriented DBMS

Document store

Time Series DBMS

Secondary database models

Graph DBMS

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

Score	0.09
Rank	#360	Overall
	#18	Object oriented DBMS

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	0.07
Rank	#375	Overall
	#41	Time Series DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

newdatabase.com

github.com/Softmotions/ejdb

opennms.github.io/newts

github.com/sitewhere/sitewhere

yanza.com

Technical documentation

dev.mobiland.com/Overview.xsp

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

github.com/OpenNMS/newts/wiki

sitewhere1.sitewhere.io/index.html

Developer

Mobiland AG

Softmotions

OpenNMS Group

SiteWhere

Yanza

Initial release

2018

2012

2014

2010

2015

Current release

1.1.263, October 2022

License

Commercial or Open Source

commercial

Open Source

GPLv2

Open Source

Apache 2.0

Open Source

Common Public Attribution License Version 1.0

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

Java

Server operating systems

Windows

server-less

Linux
OS X
Windows

Windows

Data scheme

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

schema-free

predefined scheme

schema-free

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.

Secondary indexes

SQL

Support of SQL

APIs and other access methods

.NET Client API
Proprietary client DLL
WinRT client

in-process shared library

HTTP REST
Java API

HTTP REST

HTTP API

Supported programming languages

.Net
C
C#
C++
VB.Net

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

Java

any language that supports HTTP calls

Server-side scripts

Stored procedures

Triggers

no, except callback-events from server when changes happened

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Proprietary Sharding system

none

Sharding

based on Cassandra

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

based on Cassandra

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

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

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

Windows-Profile

Users with fine-grained authorization concept

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.

More resources

Recent citations in the news

SiteWhere: An open platform for connected devices
11 July 2017, Open Source For You

11 Best Open source IoT Platforms To Develop Smart Projects
9 March 2023, H2S Media

provided by Google News

Share this page