DBMS > 4D vs. Google Cloud Datastore vs. Postgres-XL vs. SQLite vs. UniData,UniVerse

System Properties Comparison 4D vs. Google Cloud Datastore vs. Postgres-XL vs. SQLite vs. UniData,UniVerse

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

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

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Widely used embeddable, in-process RDBMS

MultiValue database and application server with SQL mapping layer and meta database capabilities

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	3.16
Rank	#97	Overall
	#2	Multivalue DBMS

Website

www.4d.com

cloud.google.com/datastore

www.postgres-xl.org

www.sqlite.org

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

Technical documentation

developer.4d.com

cloud.google.com/datastore/docs

www.postgres-xl.org/documentation

www.sqlite.org/docs.html

docs.rocketsoftware.com/bundle?cluster=true&labelkey=unidata&labelkey=prod_unidata

Developer

4D, Inc

Google

Dwayne Richard Hipp

Rocket Software

Initial release

1984

2008

2014

since 2012, originally named StormDB

2000

1985

Current release

v20, April 2023

10 R1, October 2018

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

Mozilla public license

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

Server operating systems

OS X
Windows

hosted

Linux
macOS

server-less

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

yes

not rigid because of 'dynamic typing' concept.

optional

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

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

SQL-like query language (GQL)

yes

distributed, parallel query execution

yes

SQL-92 is not fully supported

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

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

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Java API

JPA
JDBC
ODBC
OLE DB
Proprietary protocol
RESTful HTTP API
SOAP-based API

Supported programming languages

4D proprietary IDE
PHP

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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

.Net
Basic

U2 Basic
C
Java

Server-side scripts

Stored procedures

yes

using Google App Engine

user defined functions

yes

Triggers

yes

Callbacks using the Google Apps Engine

yes

U2 Basic

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication using Paxos

none

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

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

MVCC

ACID

configurable

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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, groups and roles based on Google Cloud Identity and Access Management (IAM)

fine grained access rights according to SQL-standard

Access rights according to SQL-standard and operating system based

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.