DBMS > 4D vs. Apache Druid vs. Google Cloud Datastore vs. SQLite vs. TimesTen

System Properties Comparison 4D vs. Apache Druid vs. Google Cloud Datastore vs. SQLite vs. TimesTen

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

Widely used embeddable, in-process RDBMS

In-Memory RDBMS compatible to Oracle

Primary database model

Relational DBMS

Relational DBMS
Time Series DBMS

Document store

Relational DBMS

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

Score	2.47
Rank	#110	Overall
	#54	Relational DBMS

Score	3.25
Rank	#90	Overall
	#47	Relational DBMS
	#7	Time Series DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.36
Rank	#161	Overall
	#75	Relational DBMS

Website

www.4d.com

druid.apache.org

cloud.google.com/datastore

www.sqlite.org

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

developer.4d.com

druid.apache.org/docs/latest/design

cloud.google.com/datastore/docs

www.sqlite.org/docs.html

docs.oracle.com/database/timesten-18.1

Developer

4D, Inc

Apache Software Foundation and contributors

Google

Dwayne Richard Hipp

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

1984

2012

2008

2000

1998

Current release

v20, April 2023

29.0.1, April 2024

3.46.0 (23 May 2024), May 2024

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

commercial

Open Source

Apache license v2

commercial

Open Source

Public Domain

commercial

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

Linux
OS X
Unix

hosted

server-less

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

yes

schema-less columns are supported

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

not rigid because of 'dynamic typing' concept.

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

SQL for querying

SQL-like query language (GQL)

yes

SQL-92 is not fully supported

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
RESTful HTTP/JSON API

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

4D proprietary IDE
PHP

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

.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

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

yes

using Google App Engine

PL/SQL

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

manual/auto, time-based

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes, via HDFS, S3 or other storage engines

Multi-source replication using Paxos

none

Multi-source replication
Source-replica replication

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 or Eventual Consistency depending on configuration

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

yes

Durability

Support for making data persistent

yes

by means of logfiles and checkpoints

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

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

fine grained access rights according to SQL-standard

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.