DBMS > Cassandra vs. Google Cloud Datastore vs. TimescaleDB vs. Yanza

System Properties Comparison Cassandra vs. Google Cloud Datastore vs. TimescaleDB vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Wide-column store based on ideas of BigTable and DynamoDB

Optimized for write access

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

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Time Series DBMS for IoT Applications

Primary database model

Wide column store

Document store

Time Series DBMS

Secondary database models

Vector DBMS

starting with release V5

Relational DBMS

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

Score	101.89
Rank	#12	Overall
	#1	Wide column stores

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

cassandra.apache.org

cloud.google.com/datastore

www.timescale.com

yanza.com

Technical documentation

cassandra.apache.org/doc/latest

cloud.google.com/datastore/docs

docs.timescale.com

Developer

Apache Software Foundation

Apache top level project, originally developped by Facebook

Google

Timescale

Yanza

Initial release

2008

2017

2015

Current release

4.1.3, July 2023

2.15.0, May 2024

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

Apache 2.0

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Astra DB: Multi-cloud DBaaS built on Apache Cassandra.

Implementation language

Java

Server operating systems

BSD
Linux
OS X
Windows

hosted

Linux
OS X
Windows

Windows

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

restricted

only equality queries, not always the best performing solution

yes

SQL

Support of SQL

SQL-like SELECT, DML and DDL statements (CQL)

SQL-like query language (GQL)

yes

full PostgreSQL SQL syntax

APIs and other access methods

Proprietary protocol

CQL (Cassandra Query Language, an SQL-like language)
Thrift

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

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

HTTP API

Supported programming languages

C#
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript

Node.js
Perl
PHP
Python
Ruby
Scala

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

any language that supports HTTP calls

Server-side scripts

Stored procedures

using Google App Engine

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Callbacks using the Google Apps Engine

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

Sharding

yes, across time and space (hash partitioning) attributes

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Representation of geographical distribution of servers is possible

Multi-source replication using Paxos

Source-replica replication with hot standby and reads on replicas

none

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

Eventual Consistency
Immediate Consistency

can be individually decided for each write operation

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

Atomicity and isolation are supported for single operations

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

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 can be defined per object

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

Specific characteristics

Apache Cassandra is the leading NoSQL, distributed database management system, well...
» more

Competitive advantages

No single point of failure ensures 100% availability . Operational simplicity for...
» more

Typical application scenarios

Internet of Things (IOT), fraud detection applications, recommendation engines, product...
» more

Key customers

Apple, Netflix, Uber, ING,, Intuit,Fidelity, NY Times, Outbrain, BazaarVoice, Best...
» more

Market metrics

Cassandra is used by 40% of the Fortune 100.
» more

Licensing and pricing models

Apache licenseÂ Pricing for commercial distributions provided by DataStax and available...
» 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.