DBMS > Coveo vs. GigaSpaces vs. Graph Engine vs. RocksDB

System Properties Comparison Coveo vs. GigaSpaces vs. Graph Engine vs. RocksDB

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

High performance in-memory data grid platform, powering three products: Smart Cache, Smart ODS (Operational Data Store), Smart Augmented Transactions

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Primary database model

Search engine

Document store
Object oriented DBMS

Values are user defined objects

Graph DBMS
Key-value store

Key-value store

Secondary database models

Graph DBMS
Search engine

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

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	1.03
Rank	#188	Overall
	#32	Document stores
	#6	Object oriented DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

Technical documentation

docs.coveo.com

docs.gigaspaces.com/latest/landing.html

www.graphengine.io/docs/manual

github.com/facebook/rocksdb/wiki

Developer

Coveo

Gigaspaces Technologies

Microsoft

Facebook, Inc.

Initial release

2012

2000

2010

2013

Current release

15.5, September 2020

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; Commercial licenses available

Open Source

MIT License

Open Source

BSD

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

.NET and C

C++

Server operating systems

hosted

Linux
macOS
Solaris
Windows

.NET

Linux

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

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.

XML can be used for describing objects metadata

Secondary indexes

yes

SQL

Support of SQL

SQL-99 for query and DML statements

APIs and other access methods

RESTful HTTP API

GigaSpaces LRMI
Hibernate
JCache
JDBC
JPA
ODBC
RESTful HTTP API
Spring Data

RESTful HTTP API

C++ API
Java API

Supported programming languages

C#
Java
JavaScript
Python

.Net
C++
Java
Python
Scala

C#
C++
F#
Visual Basic

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

yes, event driven architecture

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

synchronous or asynchronous
Source-replica replication

synchronous or asynchronous

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Map-Reduce pattern can be built with XAP task executors

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Consistency level configurable: ALL, QUORUM, ANY

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

Role-based access control

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.