DBMS > Graph Engine vs. InterSystems Caché vs. Oracle vs. Solr

System Properties Comparison Graph Engine vs. InterSystems Caché vs. Oracle vs. Solr

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed from the DB-Engines Ranking.

Description

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

A multi-model DBMS and application server

Widely used RDBMS

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Graph DBMS
Key-value store

Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Search engine

Secondary database models

Document store

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

Spatial DBMS

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

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

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	41.02
Rank	#24	Overall
	#3	Search engines

Website

www.graphengine.io

www.intersystems.com/products/cache

www.oracle.com/database

solr.apache.org

Technical documentation

www.graphengine.io/docs/manual

docs.intersystems.com

docs.oracle.com/en/database

solr.apache.org/resources.html

Developer

Microsoft

InterSystems

Oracle

Apache Software Foundation

Initial release

2010

1997

1980

2006

Current release

2018.1.4, May 2020

23c, September 2023

9.6.1, May 2024

License

Commercial or Open Source

Open Source

MIT License

commercial

restricted free version is available

Open Source

Apache Version 2

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

.NET and C

C and C++

Java

Server operating systems

.NET

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

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

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

yes

depending on used data model

yes

Schemaless in JSON and XML columns

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic 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

Secondary indexes

yes

All search fields are automatically indexed

SQL

Support of SQL

yes

with proprietary extensions

Solr Parallel SQL Interface

APIs and other access methods

RESTful HTTP API

.NET Client API
JDBC
ODBC
RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Java API
RESTful HTTP/JSON API

Supported programming languages

C#
C++
F#
Visual Basic

C#
C++
Java

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

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

PL/SQL

also stored procedures in Java possible

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

none

Sharding, horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

can be realized in PL/SQL

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

isolation level can be parameterized

optimistic locking

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

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

yes

User concepts

Access control

Access rights for users, groups and roles

fine grained access rights according to SQL-standard

yes

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.