DBMS > 4D vs. Amazon DynamoDB vs. Atos Standard Common Repository vs. SiteWhere vs. Yanza

System Properties Comparison 4D vs. Amazon DynamoDB vs. Atos Standard Common Repository vs. SiteWhere vs. Yanza

Editorial information provided by DB-Engines

Name

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

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

Description

Application development environment with integrated database management system

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

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

M2M integration platform for persisting/querying time series data

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Document store
Key-value store

Time Series DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	74.07
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

www.4d.com

aws.amazon.com/dynamodb

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

github.com/sitewhere/sitewhere

yanza.com

Technical documentation

developer.4d.com

docs.aws.amazon.com/dynamodb

sitewhere1.sitewhere.io/index.html

Developer

4D, Inc

Amazon

Atos Convergence Creators

SiteWhere

Yanza

Initial release

1984

2012

2016

2010

2015

Current release

v20, April 2023

1703

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

Common Public Attribution License Version 1.0

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

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

OS X
Windows

hosted

Linux

Linux
OS X
Windows

Windows

Data scheme

yes

schema-free

Schema and schema-less with LDAP views

predefined scheme

schema-free

Typing

predefined data types such as float or date

yes

optional

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

close to SQL 92

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

RESTful HTTP API

LDAP

HTTP REST

HTTP API

Supported programming languages

4D proprietary IDE
PHP

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

All languages with LDAP bindings

any language that supports HTTP calls

Server-side scripts

Stored procedures

yes

Triggers

yes

by integration with AWS Lambda

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

ACID across one or more tables within a single AWS account and region

Atomic execution of specific operations

Concurrency

Support for concurrent manipulation of data

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

Users and groups

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

LDAP bind authentication

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.