DBMS > GridGain vs. Kinetica vs. Kingbase vs. Oracle

System Properties Comparison GridGain vs. Kinetica vs. Kingbase vs. Oracle

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GridGain is an in-memory computing platform, built on Apache Ignite

Fully vectorized database across both GPUs and CPUs

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

Widely used RDBMS

Primary database model

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Spatial DBMS

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	1.48
Rank	#150	Overall
	#1	Columnar
	#26	Key-value stores
	#2	Object oriented DBMS
	#69	Relational DBMS

Score	0.42
Rank	#261	Overall
	#120	Relational DBMS

Score	0.44
Rank	#258	Overall
	#117	Relational DBMS

Score	1286.59
Rank	#1	Overall
	#1	Relational DBMS

Website

www.gridgain.com

www.kinetica.com

www.kingbase.com.cn

www.oracle.com/database

Technical documentation

www.gridgain.com/docs/index.html

docs.kinetica.com

docs.oracle.com/en/database

Developer

GridGain Systems, Inc.

Kinetica

BeiJing KINGBASE Information technologies inc.

Oracle

Initial release

2007

2012

1999

1980

Current release

GridGain 8.5.1

7.1, August 2021

V8.0, August 2021

23c, September 2023

License

Commercial or Open Source

commercial, open source

commercial

restricted free version is available

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

Java, C++, .Net, Python, REST, SQL

C, C++

C and Java

C and C++

Server operating systems

Linux
OS X
Solaris
Windows
z/OS

Linux

Linux
Windows

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

Data scheme

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.

yes

Secondary indexes

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

SQL-like DML and DDL statements

Standard with numerous extensions

yes

with proprietary extensions

APIs and other access methods

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

JDBC
ODBC
RESTful HTTP API

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C++
Java
JavaScript (Node.js)
Python

.Net
C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
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

yes (compute grid and cache interceptors can be used instead)

user defined functions

PL/SQL

also stored procedures in Java possible

Triggers

yes (cache interceptors and events)

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding, horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

Source-replica replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate 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

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

GPU vRAM or System RAM

yes

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

User concepts

Access control

Role-based access control
Security Hooks for custom implementations

Access rights for users and roles on table level

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.