DBMS > Coveo vs. JaguarDB vs. Oracle vs. Rockset

System Properties Comparison Coveo vs. JaguarDB vs. Oracle vs. Rockset

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

Performant, highly scalable DBMS for AI and IoT applications

Widely used RDBMS

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Search engine

Key-value store
Vector DBMS

Relational DBMS

Document store

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Relational 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	0.06
Rank	#381	Overall
	#59	Key-value stores
	#14	Vector DBMS

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	0.82
Rank	#212	Overall
	#36	Document stores

Website

www.coveo.com

www.jaguardb.com

www.oracle.com/database

rockset.com

Technical documentation

docs.coveo.com

www.jaguardb.com/support.html

docs.oracle.com/en/database

docs.rockset.com

Developer

Coveo

DataJaguar, Inc.

Oracle

Rockset

Initial release

2012

2015

1980

2019

Current release

3.3 July 2023

23c, September 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

commercial

restricted free version is available

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

C++

the server part. Clients available in other languages

C and C++

C++

Server operating systems

hosted

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

hosted

Data scheme

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

yes

Schemaless in JSON and XML columns

schema-free

Typing

predefined data types such as float or date

yes

dynamic typing

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

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

SQL

Support of SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

yes

with proprietary extensions

Read-only SQL queries, including JOINs

APIs and other access methods

RESTful HTTP API

JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

HTTP REST

Supported programming languages

C#
Java
JavaScript
Python

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

PL/SQL

also stored procedures in Java possible

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

Sharding, horizontal partitioning

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

isolation level can be parameterized

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

Version 12c introduced the new option 'Oracle Database In-Memory'

User concepts

Access control

granular access controls, API key management, content filters

rights management via user accounts

fine grained access rights according to SQL-standard

Access rights for users and organizations can be defined via Rockset console

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.