DBMS > Amazon Redshift vs. Pinecone vs. Tigris vs. Tkrzw

System Properties Comparison Amazon Redshift vs. Pinecone vs. Tigris vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A managed, cloud-native vector database

A horizontally scalable, ACID transactional, document database available both as a fully managed cloud service and for deployment on self-managed infrastructure

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Relational DBMS

Vector DBMS

Document store
Key-value store
Search engine
Time Series DBMS

Key-value store

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	3.23
Rank	#92	Overall
	#3	Vector DBMS

Score	0.09
Rank	#363	Overall
	#49	Document stores
	#54	Key-value stores
	#22	Search engines
	#38	Time Series DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

aws.amazon.com/redshift

www.pinecone.io

www.tigrisdata.com

dbmx.net/tkrzw

Technical documentation

docs.aws.amazon.com/redshift

docs.pinecone.io/docs/overview

www.tigrisdata.com/docs

Developer

Amazon (based on PostgreSQL)

Pinecone Systems, Inc

Tigris Data, Inc.

Mikio Hirabayashi

Initial release

2012

2019

2022

2020

Current release

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Apache Version 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

C++

Server operating systems

hosted

Linux
macOS
Windows

Linux
macOS

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

String, Number, Boolean

yes

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

CLI Client
gRPC
RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

Python

Go
Java
JavaScript (Node.js)

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

in Python

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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

yes, using FoundationDB

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using specific database classes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights for users and roles

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.