DBMS > Coveo vs. Galaxybase vs. Ingres vs. Oracle

System Properties Comparison Coveo vs. Galaxybase vs. Ingres vs. Oracle

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

Scalable, ACID-compliant native distributed parallel graph platform

Well established RDBMS

Widely used RDBMS

Primary database model

Search engine

Graph DBMS

Relational DBMS

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

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
	#39	Graph DBMS

Score	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Website

www.coveo.com

galaxybase.com

www.actian.com/databases/ingres

www.oracle.com/database

Technical documentation

docs.coveo.com

docs.actian.com/ingres

docs.oracle.com/en/database

Developer

Coveo

Chuanglin(Createlink) Technology Co., Ltd 浙江创邻科技有限公司

Actian Corporation

Oracle

Initial release

2012

2017

1974

originally developed at University Berkely in early 1970s

1980

Current release

Nov 20, November 2021

11.2, May 2022

23c, September 2023

License

Commercial or Open Source

commercial

restricted free version is 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 and Java

C and C++

Server operating systems

hosted

Linux

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

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

Data scheme

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

Strong typed schema

yes

Schemaless in JSON and XML columns

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.

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API

Browser interface
console (shell)
Graph API (Gremlin)
OpenCypher
Proprietary native API

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

C#
Java
JavaScript
Python

Go
Java
Python

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

Server-side scripts

Stored procedures

user defined procedures and functions

yes

PL/SQL

also stored procedures in Java possible

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Ingres Replicator

Multi-source replication
Source-replica replication

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

Foreign keys

Referential integrity

yes

Relationships in graphs

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

MVCC

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

Role-based access control

fine grained access rights 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.