DBMS > AgensGraph vs. Amazon Redshift vs. Solr vs. Teradata

System Properties Comparison AgensGraph vs. Amazon Redshift vs. Solr vs. Teradata

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

Large scale data warehouse service for use with business intelligence tools

A widely used distributed, scalable search engine based on Apache Lucene

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Graph DBMS
Relational DBMS

Relational DBMS

Search engine

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Score	45.33
Rank	#21	Overall
	#15	Relational DBMS

Website

bitnine.net/agensgraph

aws.amazon.com/redshift

solr.apache.org

www.teradata.com

Technical documentation

bitnine.net/documentation

docs.aws.amazon.com/redshift

solr.apache.org/resources.html

docs.teradata.com

Developer

Bitnine Global Inc.

Amazon (based on PostgreSQL)

Apache Software Foundation

Teradata

Initial release

2016

2012

2006

1984

Current release

2.1, December 2018

9.6.0, April 2024

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Apache Version 2

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

Java

Server operating systems

Linux
OS X
Windows

hosted

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

hosted
Linux

Data scheme

depending on used data model

yes

Dynamic Fields enables on-the-fly addition of new fields

yes

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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.

yes

Secondary indexes

yes

restricted

yes

All search fields are automatically indexed

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

does not fully support an SQL-standard

Solr Parallel SQL Interface

yes

SQL 2016 + extensions

APIs and other access methods

Cypher Query Language
JDBC

JDBC
ODBC

Java API
RESTful HTTP/JSON API

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

C
Java
JavaScript
Python

All languages supporting JDBC/ODBC

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

yes

user defined functions

in Python

Java plugins

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

User configurable commands triggered on index changes

yes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate 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

optimistic locking

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

yes

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.