DBMS > Coveo vs. IRONdb vs. Oracle vs. Teradata Aster

System Properties Comparison Coveo vs. IRONdb vs. Oracle vs. Teradata Aster

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

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

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Widely used RDBMS

Platform for big data analytics on multistructured data sources and types

Primary database model

Search engine

Time Series 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.11
Rank	#118	Overall
	#11	Search engines

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Website

www.coveo.com

www.circonus.com/solutions/time-series-database/

www.oracle.com/database

Technical documentation

docs.coveo.com

docs.circonus.com/irondb/category/getting-started

docs.oracle.com/en/database

Developer

Coveo

Circonus LLC.

Oracle

Teradata

Initial release

2012

2017

1980

2005

Current release

V0.10.20, January 2018

23c, September 2023

License

Commercial or Open Source

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 and C++

Server operating systems

hosted

Linux

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

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

Schemaless in JSON and XML columns

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

Typing

predefined data types such as float or date

yes

text, numeric, histograms

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.

yes

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

with proprietary extensions

yes

APIs and other access methods

RESTful HTTP API

HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

C#
Java
JavaScript
Python

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
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

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

yes, in Lua

PL/SQL

also stored procedures in Java possible

R packages

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Automatic, metric affinity per node

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

configurable replication factor, datacenter aware

Multi-source replication
Source-replica replication

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

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

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

User concepts

Access control

granular access controls, API key management, content filters

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.