DBMS > GridDB vs. MarkLogic vs. Oracle vs. Tkrzw

System Properties Comparison GridDB vs. MarkLogic vs. Oracle vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable in-memory time series database optimized for IoT and Big Data

Operational and transactional Enterprise NoSQL database

Widely used RDBMS

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Time Series DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Key-value store

Secondary database models

Key-value store
Relational 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.95
Rank	#128	Overall
	#10	Time Series DBMS

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	1236.29
Rank	#1	Overall
	#1	Relational DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

griddb.net

www.marklogic.com

www.oracle.com/database

dbmx.net/tkrzw

Technical documentation

docs.griddb.net

docs.marklogic.com

docs.oracle.com/en/database

Developer

Toshiba Corporation

MarkLogic Corp.

Oracle

Mikio Hirabayashi

Initial release

2013

2001

1980

2020

Current release

5.1, August 2022

11.0, December 2022

23c, September 2023

0.9.3, August 2020

License

Commercial or Open Source

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

restricted free version is available

commercial

restricted free version is available

Open Source

Apache Version 2.0

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

C++

C and C++

C++

Server operating systems

Linux

Linux
OS X
Windows

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

Linux
macOS

Data scheme

yes

schema-free

Schema can be enforced

yes

Schemaless in JSON and XML columns

schema-free

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

SQL92, SQL-like TQL (Toshiba Query Language)

yes

SQL92

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

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

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

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++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

PL/SQL

also stored procedures in Java possible

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency within container, eventual consistency across containers

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID at container level

ACID

can act as a resource manager in an XA/JTA transaction

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

yes, with Range Indexes

yes

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

yes

using specific database classes

User concepts

Access control

Access rights for users can be defined per database

Role-based access control at the document and subdocument levels

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.