DBMS > 4D vs. Altibase vs. Google Cloud Datastore vs. SiteWhere vs. SQLite

System Properties Comparison 4D vs. Altibase vs. Google Cloud Datastore vs. SiteWhere vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

An enterprise grade, high-performance RDBMS

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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	1.02
Rank	#189	Overall
	#88	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

www.4d.com

altibase.com

cloud.google.com/datastore

github.com/sitewhere/sitewhere

www.sqlite.org

Technical documentation

developer.4d.com

github.com/ALTIBASE/Documents/tree/master/Manuals

cloud.google.com/datastore/docs

sitewhere1.sitewhere.io/index.html

www.sqlite.org/docs.html

Developer

4D, Inc

Altibase

Google

SiteWhere

Dwayne Richard Hipp

Initial release

1984

1999

2008

2010

2000

Current release

v20, April 2023

v7.3, 2023, August 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Open source edition discontinued with March 2023

commercial

Open Source

Common Public Attribution License Version 1.0

Open Source

Public Domain

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

C++

Java

Server operating systems

OS X
Windows

AIX
HP-UX
Linux

hosted

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

yes, details here

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

ANSI SQL-92

SQL-like query language (GQL)

yes

SQL-92 is not fully supported

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC
Proprietary protocol

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

4D proprietary IDE
PHP

C
C++
Java

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

stored procedures and stored functions

using Google App Engine

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication using Paxos

selectable replication factor

based on HBase

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

fine grained access rights according to SQL-standard

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.