DBMS > 4D vs. Amazon DynamoDB vs. Hazelcast vs. jBASE vs. SiteWhere

System Properties Comparison 4D vs. Amazon DynamoDB vs. Hazelcast vs. jBASE vs. SiteWhere

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

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

A widely adopted in-memory data grid

A robust multi-value DBMS comprising development tools and middleware

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS

Document store
Key-value store

Key-value store

Multivalue DBMS

Time Series DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	2.47
Rank	#110	Overall
	#54	Relational DBMS

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

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

www.4d.com

aws.amazon.com/dynamodb

hazelcast.com

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

github.com/sitewhere/sitewhere

Technical documentation

developer.4d.com

docs.aws.amazon.com/dynamodb

hazelcast.org/imdg/docs

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

sitewhere1.sitewhere.io/index.html

Developer

4D, Inc

Amazon

Hazelcast

Rocket Software (formerly Zumasys)

SiteWhere

Initial release

1984

2012

2008

1991

2010

Current release

v20, April 2023

5.3.6, November 2023

5.7

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

Common Public Attribution License Version 1.0

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

Server operating systems

OS X
Windows

hosted

All OS with a Java VM

AIX
Linux
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

predefined scheme

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

the object must implement a serialization strategy

yes

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

SQL-like query language

Embedded SQL for jBASE in BASIC

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

RESTful HTTP API

JCache
JPA
Memcached protocol
RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

HTTP REST

Supported programming languages

4D proprietary IDE
PHP

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

.Net
Basic
Jabbascript
Java

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

Triggers

yes

by integration with AWS Lambda

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Replicated Map

yes

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

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 selectable by user

Raft Consensus Algorithm

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

one or two-phase-commit; repeatable reads; read commited

ACID

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)

Role-based access control

Access rights can be defined down to the item level

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.