DBMS > Amazon DynamoDB vs. Apache Phoenix vs. Coveo vs. GridGain

System Properties Comparison Amazon DynamoDB vs. Apache Phoenix vs. Coveo vs. GridGain

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Hosted, scalable database service by Amazon with the data stored in Amazons cloud

A scale-out RDBMS with evolutionary schema built on Apache HBase

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

GridGain is an in-memory computing platform, built on Apache Ignite

Primary database model

Document store
Key-value store

Relational DBMS

Search engine

Key-value store
Relational DBMS

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

Score	74.45
Rank	#17	Overall
	#3	Document stores
	#2	Key-value stores

Score	2.06
Rank	#123	Overall
	#58	Relational DBMS

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Website

aws.amazon.com/dynamodb

phoenix.apache.org

www.coveo.com

www.gridgain.com

Technical documentation

docs.aws.amazon.com/dynamodb

phoenix.apache.org

docs.coveo.com

www.gridgain.com/docs/index.html

Developer

Amazon

Apache Software Foundation

Coveo

GridGain Systems, Inc.

Initial release

2012

2014

2012

2007

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

GridGain 8.5.1

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

Open Source

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

Java

Java, C++, .Net

Server operating systems

hosted

Linux
Unix
Windows

hosted

Linux
OS X
Solaris
Windows

Data scheme

schema-free

yes

late-bound, schema-on-read capabilities

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

yes

Typing

predefined data types such as float or date

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

SQL

Support of SQL

yes

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

RESTful HTTP API

JDBC

RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

C#
Java
JavaScript
Python

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

user defined functions

yes (compute grid and cache interceptors can be used instead)

Triggers

yes

by integration with AWS Lambda

yes

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

yes (replicated cache)

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Hadoop integration

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID across one or more tables within a single AWS account and region

ACID

yes

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

Access rights for users and roles can be defined via the AWS Identity and Access Management (IAM)

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

granular access controls, API key management, content filters

Security Hooks for custom implementations

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.