DBMS > 4D vs. Ehcache vs. jBASE vs. SiteWhere vs. SQLite

System Properties Comparison 4D vs. Ehcache vs. jBASE vs. SiteWhere vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

A widely adopted Java cache with tiered storage options

A robust multi-value DBMS comprising development tools and middleware

M2M integration platform for persisting/querying time series data

Widely used embeddable, in-process RDBMS

Primary database model

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

Score	2.47
Rank	#110	Overall
	#54	Relational DBMS

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	1.49
Rank	#156	Overall
	#3	Multivalue DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

www.4d.com

www.ehcache.org

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

github.com/sitewhere/sitewhere

www.sqlite.org

Technical documentation

developer.4d.com

www.ehcache.org/documentation

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

sitewhere1.sitewhere.io/index.html

www.sqlite.org/docs.html

Developer

4D, Inc

Terracotta Inc, owned by Software AG

Rocket Software (formerly Zumasys)

SiteWhere

Dwayne Richard Hipp

Initial release

1984

2009

1991

2010

2000

Current release

v20, April 2023

3.10.0, March 2022

5.7

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

Common Public Attribution License Version 1.0

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

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

All OS with a Java VM

AIX
Linux
Windows

Linux
OS X
Windows

server-less

Data scheme

yes

schema-free

predefined scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

optional

yes

not rigid because of 'dynamic typing' concept.

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

Embedded SQL for jBASE in BASIC

yes

SQL-92 is not fully supported

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JCache

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

4D proprietary IDE
PHP

Java

.Net
Basic
Jabbascript
Java

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

by using Terracotta Server

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

by using Terracotta Server

yes

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

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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 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.