DBMS > Amazon Redshift vs. EXASOL vs. JaguarDB vs. Pinecone

System Properties Comparison Amazon Redshift vs. EXASOL vs. JaguarDB vs. Pinecone

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Performant, highly scalable DBMS for AI and IoT applications

A managed, cloud-native vector database

Primary database model

Relational DBMS

Key-value store
Vector DBMS

Vector DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#15	Vector DBMS

Score	3.23
Rank	#92	Overall
	#3	Vector DBMS

Website

aws.amazon.com/redshift

www.exasol.com

www.jaguardb.com

www.pinecone.io

Technical documentation

docs.aws.amazon.com/redshift

www.exasol.com/resources

www.jaguardb.com/support.html

docs.pinecone.io/docs/overview

Developer

Amazon (based on PostgreSQL)

Exasol

DataJaguar, Inc.

Pinecone Systems, Inc

Initial release

2012

2000

2015

2019

Current release

3.3 July 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

commercial

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++

the server part. Clients available in other languages

Server operating systems

hosted

Linux

hosted

Data scheme

yes

Typing

predefined data types such as float or date

yes

String, Number, Boolean

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

yes

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

JDBC
ODBC

.Net
JDBC
ODBC
WebSocket

JDBC
ODBC

RESTful HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

Java
Lua
Python
R

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Python

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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 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 according to SQL-standard

rights management via user accounts

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.