DBMS > Geode vs. Linter vs. MarkLogic vs. Oracle Rdb vs. Snowflake

System Properties Comparison Geode vs. Linter vs. MarkLogic vs. Oracle Rdb vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

RDBMS for high security requirements

Operational and transactional Enterprise NoSQL database

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Key-value store

Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

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

Score	1.08
Rank	#184	Overall
	#85	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

geode.apache.org

linter.ru

www.marklogic.com

www.oracle.com/database/technologies/related/rdb.html

www.snowflake.com

Technical documentation

geode.apache.org/docs

docs.marklogic.com

www.oracle.com/database/technologies/related/rdb-doc.html

docs.snowflake.net/manuals/index.html

Developer

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

relex.ru

MarkLogic Corp.

Oracle, originally developed by Digital Equipment Corporation (DEC)

Snowflake Computing Inc.

Initial release

2002

1990

2001

1984

2014

Current release

1.1, February 2017

11.0, December 2022

7.4.1.1, 2021

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Java

C and C++

C++

Server operating systems

All OS with a Java VM

the JDK (8 or later) is also required

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux
OS X
Windows

HP Open VMS

hosted

Data scheme

schema-free

yes

schema-free

Schema can be enforced

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

yes

support of semi-structured data formats (JSON, XML, Avro)

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

SQL-like query language (OQL)

yes

SQL92

yes

APIs and other access methods

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

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

CLI Client
JDBC
ODBC

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

via XQuery or JavaScript

user defined functions

Triggers

yes

Cache Event Listeners

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

ACID

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

yes, on a single node

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

yes, with Range Indexes

User concepts

Access control

Access rights per client and object definable

fine grained access rights according to SQL-standard

Role-based access control at the document and subdocument levels

Users with fine-grained authorization concept, user roles and pluggable authentication

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.