DBMS > Apache Kylin vs. Google Cloud Datastore vs. Snowflake vs. TypeDB vs. XTDB

System Properties Comparison Apache Kylin vs. Google Cloud Datastore vs. Snowflake vs. TypeDB vs. XTDB

Editorial information provided by DB-Engines

Name

Description

A distributed analytics engine for big data, providing a SQL interface and multi-dimensional analysis (OLAP) and leveraging the Hadoop stack

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

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

TypeDB is a strongly-typed database with a rich and logical type system and TypeQL as its query language

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

Primary database model

Relational DBMS

Document store

Relational DBMS

Graph DBMS
Relational DBMS

Often described as a 'hyper-relational' database, since it implements the 'Entity-Relationship Paradigm' to manage complex data structures and ontologies.

Document store

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

Score	1.18
Rank	#172	Overall
	#79	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.65
Rank	#234	Overall
	#20	Graph DBMS
	#107	Relational DBMS

Score	0.11
Rank	#343	Overall
	#46	Document stores

Website

kylin.apache.org

cloud.google.com/datastore

www.snowflake.com

typedb.com

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

Technical documentation

kylin.apache.org/docs

cloud.google.com/datastore/docs

docs.snowflake.net/manuals/index.html

typedb.com/docs

www.xtdb.com/docs

Developer

Apache Software Foundation, originally contributed from eBay Inc

Google

Snowflake Computing Inc.

Vaticle

Juxt Ltd.

Initial release

2015

2008

2014

2016

2019

Current release

3.1.0, July 2020

2.26.3, January 2024

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

commercial

Open Source

GPL Version 3, commercial licenses available

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

Java

Clojure

Server operating systems

Linux

hosted

Linux
OS X
Windows

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

yes, details here

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

Secondary indexes

yes

SQL

Support of SQL

ANSI SQL for queries (using Apache Calcite)

SQL-like query language (GQL)

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

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

CLI Client
JDBC
ODBC

gRPC protocol
TypeDB Console (shell)
TypeDB Studio (Visualisation software- previously TypeDB Workbase)

HTTP REST
JDBC

Supported programming languages

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

JavaScript (Node.js)
Python

All JVM based languages
Groovy
Java
JavaScript (Node.js)
Python
Scala

Clojure
Java

Server-side scripts

Stored procedures

using Google App Engine

user defined functions

Triggers

Callbacks using the Google Apps Engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

by using Cassandra

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

yes

Multi-source replication

by using Cassandra

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

by using Apache Kafka and Apache Zookeeper

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

substituted by the relationship feature

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

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.

User concepts

Access control

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

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

yes

at REST API level; other APIs in progress

More information provided by the system vendor

Specific characteristics

TypeDB is a polymorphic database with a conceptual data model, a strong subtyping...
» more

Competitive advantages

TypeDB provides a new level of expressivity, extensibility, interoperability, and...
» more

Typical application scenarios

Life sciences : TypeDB makes working with biological data much easier and accelerates...
» more

Licensing and pricing models

Apache f or language drivers, and AGPL and Commercial for the database server. The...
» more

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.