DBMS > 4D vs. EXASOL vs. Google Cloud Datastore vs. SwayDB vs. XTDB

System Properties Comparison 4D vs. EXASOL vs. Google Cloud Datastore vs. SwayDB vs. XTDB

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

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

An embeddable, non-blocking, type-safe key-value store for single or multiple disks and in-memory storage

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	1.99
Rank	#124	Overall
	#58	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.00
Rank	#382	Overall
	#59	Key-value stores

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

www.4d.com

www.exasol.com

cloud.google.com/datastore

swaydb.simer.au

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

developer.4d.com

www.exasol.com/resources

cloud.google.com/datastore/docs

www.xtdb.com/docs

Developer

4D, Inc

Exasol

Google

Simer Plaha

Juxt Ltd.

Initial release

1984

2000

2008

2018

2019

Current release

v20, April 2023

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

GNU Affero GPL V3.0

Open Source

MIT License

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

Scala

Clojure

Server operating systems

OS X
Windows

hosted

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

yes, extensible-data-notation format

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

yes

SQL-like query language (GQL)

limited SQL, making use of Apache Calcite

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

.Net
JDBC
ODBC
WebSocket

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

HTTP REST
JDBC

Supported programming languages

4D proprietary IDE
PHP

Java
Lua
Python
R

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

Java
Kotlin
Scala

Clojure
Java

Server-side scripts

Stored procedures

yes

user defined functions

using Google App Engine

Triggers

yes

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Multi-source replication using Paxos

none

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

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

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Atomic execution of operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

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 according to SQL-standard

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

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

Recent citations in the news

Mathias Golombek, Chief Technology Officer of Exasol – Interview Series
21 May 2024, Unite.AI

Exasol Finds AI Underinvestment Leads to Business Failure, But Data Challenges Stall Rapid Adoption
14 May 2024, insideBIGDATA

It's Back to the Database Future for Exasol CEO Tewes
26 October 2023, Datanami

Exasol gets jolt of AI with Espresso suite of capabilities
26 February 2024, TechTarget

Exasol Unveils New Suite of AI Tools to Turbocharge Enterprise Data Analytics
21 February 2024, Business Wire

provided by Google News

Best cloud storage of 2024
21 May 2024, TechRadar

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Google says it'll stop charging fees to transfer data out of Google Cloud
11 January 2024, TechCrunch

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

provided by Google News

Share this page