DBMS > Amazon Redshift vs. Google Cloud Spanner vs. Graphite vs. Qdrant vs. TimescaleDB

System Properties Comparison Amazon Redshift vs. Google Cloud Spanner vs. Graphite vs. Qdrant vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

A high-performance vector database with neural network or semantic-based matching

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

Primary database model

Secondary database models

Relational DBMS

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

Score	15.25
Rank	#38	Overall
	#23	Relational DBMS

Score	2.69
Rank	#101	Overall
	#51	Relational DBMS

Score	5.19
Rank	#62	Overall
	#4	Time Series DBMS

Score	1.53
Rank	#145	Overall
	#7	Vector DBMS

Score	4.06
Rank	#73	Overall
	#5	Time Series DBMS

Website

aws.amazon.com/redshift

cloud.google.com/spanner

github.com/graphite-project/graphite-web

github.com/qdrant/qdrant
qdrant.tech

www.timescale.com

Technical documentation

docs.aws.amazon.com/redshift

cloud.google.com/spanner/docs

graphite.readthedocs.io

qdrant.tech/documentation

docs.timescale.com

Developer

Amazon (based on PostgreSQL)

Google

Chris Davis

Qdrant

Timescale

Initial release

2012

2017

2006

2021

2017

Current release

2.15.0, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2.0

Open Source

Apache 2.0

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

Python

Rust

Server operating systems

hosted

Linux
Unix

Docker
Linux
macOS
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

Numeric data only

Numbers, Strings, Geo, Boolean

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

yes

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

Query statements complying to ANSI 2011

yes

full PostgreSQL SQL syntax

APIs and other access methods

JDBC
ODBC

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

HTTP API
Sockets

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

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

Supported programming languages

All languages supporting JDBC/ODBC

Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in Python

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

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication with 3 replicas for regional instances.

none

Collection-level replication

Source-replica replication with hot standby and reads on replicas

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

none

Eventual Consistency, tunable consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

yes

Transaction concepts

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

ACID

Strict serializable isolation

ACID

Concurrency

Support for concurrent manipulation of data

yes

locking

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

fine grained access rights according to SQL-standard

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

Key-based authentication

fine grained access rights according to SQL-standard

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.