DBMS > 4D vs. Rockset vs. Snowflake vs. TerminusDB vs. XTDB

System Properties Comparison 4D vs. Rockset vs. Snowflake vs. TerminusDB vs. XTDB

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Cloud-based data warehousing service for structured and semi-structured data

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

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

Primary database model

Secondary database models

Relational DBMS
Search engine

Document store
RDF store

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

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

Technical documentation

developer.4d.com

docs.rockset.com

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

www.xtdb.com/docs

Developer

4D, Inc

Rockset

Snowflake Computing Inc.

DataChemist Ltd.

Juxt Ltd.

Initial release

1984

2019

2014

2018

2019

Current release

v20, April 2023

11.0.0, January 2023

1.19, September 2021

License

Commercial or Open Source

commercial

Open Source

GPL V3

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

C++

Prolog, Rust

Clojure

Server operating systems

OS X
Windows

hosted

Linux

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

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

schema-free

Typing

predefined data types such as float or date

yes

dynamic typing

yes

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

ingestion from XML files supported

yes

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

close to SQL 92

Read-only SQL queries, including JOINs

yes

SQL-like query language (WOQL)

limited SQL, making use of Apache Calcite

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

HTTP REST

CLI Client
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

HTTP REST
JDBC

Supported programming languages

4D proprietary IDE
PHP

Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

JavaScript
Python

Clojure
Java

Server-side scripts

Stored procedures

yes

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

Automatic sharding

yes

Graph Partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Journaling Streams

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory journaling

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.

User concepts

Access control

Users and groups

Access rights for users and organizations can be defined via Rockset console

Users with fine-grained authorization concept, user roles and pluggable authentication

Role-based access control

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.