DBMS > Coveo vs. OrigoDB vs. RocksDB vs. SAP SQL Anywhere vs. Splunk

System Properties Comparison Coveo vs. OrigoDB vs. RocksDB vs. SAP SQL Anywhere vs. Splunk

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

A fully ACID in-memory object graph database

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

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Analytics Platform for Big Data

Primary database model

Search engine

Document store
Object oriented DBMS

Key-value store

Relational DBMS

Search engine

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	3.65
Rank	#85	Overall
	#11	Key-value stores

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

www.coveo.com

origodb.com

rocksdb.org

www.sap.com/products/technology-platform/sql-anywhere.html

www.splunk.com

Technical documentation

docs.coveo.com

origodb.com/docs

github.com/facebook/rocksdb/wiki

help.sap.com/docs/SAP_SQL_Anywhere

docs.splunk.com/Documentation/Splunk

Developer

Coveo

Robert Friberg et al

Facebook, Inc.

SAP

formerly Sybase

Splunk Inc.

Initial release

2012

2009

under the name LiveDB

2013

1992

2003

Current release

8.11.4, April 2024

17, July 2015

License

Commercial or Open Source

commercial

Open Source

BSD

commercial

Limited free edition and free developer edition 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
Windows

Linux

AIX
HP-UX
Linux
OS X
Solaris
Windows

Linux
OS X
Solaris
Windows

Data scheme

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

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

yes

Secondary indexes

yes

SQL

Support of SQL

yes

Splunk Search Processing Language for search commands

APIs and other access methods

RESTful HTTP API

.NET Client API
HTTP API
LINQ

C++ API
Java API

ADO.NET
HTTP API
JDBC
ODBC

HTTP REST

Supported programming languages

C#
Java
JavaScript
Python

.Net

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

yes, in C/C++, Java, .Net or Perl

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

yes

horizontal partitioning

client side managed; servers are not synchronized

horizontal partitioning

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

yes

Source-replica replication

Database mirroring

Multi-source replication

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

Foreign keys

Referential integrity

yes

depending on model

yes

Transaction concepts

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

yes

ACID

yes

ACID

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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 authorization

fine grained access rights according to SQL-standard

Access rights for users and roles

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.