DBMS > Coveo vs. Firebase Realtime Database vs. Riak KV vs. SAP HANA

System Properties Comparison Coveo vs. Firebase Realtime Database vs. Riak KV vs. SAP HANA

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Distributed, fault tolerant key-value store

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Search engine

Document store

Key-value store

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

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	13.64
Rank	#39	Overall
	#6	Document stores

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

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.coveo.com

firebase.google.com/products/realtime-database

www.sap.com/products/hana.html

Technical documentation

docs.coveo.com

firebase.google.com/docs/database

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

help.sap.com/hana

Developer

Coveo

Google

acquired by Google 2014

OpenSource, formerly Basho Technologies

SAP

Initial release

2012

2009

2010

Current release

3.2.0, December 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Erlang

Server operating systems

hosted

Linux
OS X

Appliance or cloud-service

Data scheme

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.

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

APIs and other access methods

RESTful HTTP API

Android
iOS
JavaScript API
RESTful HTTP API

HTTP API
Native Erlang Interface

JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Python

Java
JavaScript
Objective-C

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

limited functionality with using 'rules'

Erlang

SQLScript, R

Triggers

yes

Callbacks are triggered when data changes

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

no "single point of failure"

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

yes

Transaction concepts

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

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

granular access controls, API key management, content filters

yes, based on authentication and database rules

yes, using Riak Security

yes

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.