DBMS > Amazon DynamoDB vs. Coveo vs. Google Cloud Bigtable vs. OceanBase

System Properties Comparison Amazon DynamoDB vs. Coveo vs. Google Cloud Bigtable vs. OceanBase

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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

A distributed, high available RDBMS compatible with Oracle and MySQL

Primary database model

Document store
Key-value store

Search engine

Key-value store
Wide column store

Relational DBMS

Secondary database models

Document store
Wide column store

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	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	1.57
Rank	#149	Overall
	#69	Relational DBMS

Website

aws.amazon.com/dynamodb

www.coveo.com

cloud.google.com/bigtable

en.oceanbase.com

Technical documentation

docs.aws.amazon.com/dynamodb

docs.coveo.com

cloud.google.com/bigtable/docs

en.oceanbase.com/docs/oceanbase-database

Developer

Amazon

Coveo

Google

OceanBase

previously Alibaba and Ant Group

Initial release

2012

2015

2010

Current release

4.3.0, April 2024

License

Commercial or Open Source

commercial

free tier for a limited amount of database operations

commercial

Open Source

Commercial license available

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

Data scheme

schema-free

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

schema-free

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

APIs and other access methods

RESTful HTTP API

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Proprietary native API
Table API

Supported programming languages

.Net
ColdFusion
Erlang
Groovy
Java
JavaScript
Perl
PHP
Python
Ruby

C#
Java
JavaScript
Python

C#
C++
Go
Java
JavaScript (Node.js)
Python

Ada

in MySQL-compatible model
C

in Oracle- and MySQL- compatible models
C++

in Oracle- and MySQL- compatible models
D

in MySQL-compatible model
Delphi

in MySQL-compatible model
Eiffel

in MySQL-compatible model
Erlang

in MySQL-compatible model
Haskell

in MySQL-compatible model
Java

in Oracle- and MySQL- compatible models
JavaScript (Node.js)

in MySQL-compatible model
Objective-C

in MySQL-compatible model
OCaml

in MySQL-compatible model
Perl

in MySQL-compatible model
PHP

in MySQL-compatible model
Python

in MySQL-compatible model
Ruby

in MySQL-compatible model
Scheme

in MySQL-compatible model
Tcl

in MySQL-compatible model

Server-side scripts

Stored procedures

PL/SQL in oracle-compatible mode, MySQL Stored Procedure in mysql-compatible mode

Triggers

yes

by integration with AWS Lambda

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

horizontal partitioning (by hash, key, range, range columns, list, and list columns)

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Internal replication in Colossus, and regional replication between two clusters in different zones

Multi-source replication using Paxos

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

can be specified for read operations

Immediate Consistency

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

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

yes

Atomic single-row operations

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.

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Access rights for users, groups and roles 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.