DBMS > Amazon DynamoDB vs. Coveo vs. GridGain vs. Riak KV

System Properties Comparison Amazon DynamoDB vs. Coveo vs. GridGain vs. Riak KV

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

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

Distributed, fault tolerant key-value store

Primary database model

Document store
Key-value store

Search engine

Key-value store
Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

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.11
Rank	#118	Overall
	#11	Search engines

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

Score	4.01
Rank	#79	Overall
	#9	Key-value stores

Website

aws.amazon.com/dynamodb

www.coveo.com

www.gridgain.com

Technical documentation

docs.aws.amazon.com/dynamodb

docs.coveo.com

www.gridgain.com/docs/index.html

www.tiot.jp/riak-docs/riak/kv/latest

Developer

Amazon

Coveo

GridGain Systems, Inc.

OpenSource, formerly Basho Technologies

Initial release

2012

2007

2009

Current release

GridGain 8.5.1

3.2.0, December 2022

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

Apache version 2, commercial enterprise edition

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, C++, .Net

Erlang

Server operating systems

hosted

Linux
OS X
Solaris
Windows

Linux
OS X

Data scheme

schema-free

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

yes

schema-free

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

restricted

SQL

Support of SQL

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

APIs and other access methods

RESTful HTTP API

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

HTTP API
Native Erlang Interface

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
Java
JavaScript
Python

C#
C++
Java
PHP
Python
Ruby
Scala

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

Server-side scripts

Stored procedures

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

Erlang

Triggers

yes

by integration with AWS Lambda

yes

yes (cache interceptors and events)

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes (replicated cache)

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes (compute grid and hadoop accelerator)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

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

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)

granular access controls, API key management, content filters

Security Hooks for custom implementations

yes, using Riak Security

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.