DBMS > Hazelcast vs. Oracle Coherence vs. Percona Server for MongoDB vs. SQLite

System Properties Comparison Hazelcast vs. Oracle Coherence vs. Percona Server for MongoDB vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted in-memory data grid

Oracles in-memory data grid solution

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Widely used embeddable, in-process RDBMS

Primary database model

Key-value store

Document store

Relational DBMS

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	5.46
Rank	#61	Overall
	#7	Key-value stores

Score	1.97
Rank	#129	Overall
	#22	Key-value stores

Score	0.60
Rank	#246	Overall
	#39	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

hazelcast.com

www.oracle.com/java/coherence

www.percona.com/mongodb/software/percona-server-for-mongodb

www.sqlite.org

Technical documentation

hazelcast.org/imdg/docs

docs.oracle.com/en/middleware/standalone/coherence

docs.percona.com/percona-distribution-for-mongodb

www.sqlite.org/docs.html

Developer

Hazelcast

Oracle

Percona

Dwayne Richard Hipp

Initial release

2008

2007

2015

2000

Current release

5.3.6, November 2023

14.1, August 2023

3.4.10-2.10, November 2017

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

GPL Version 2

Open Source

Public Domain

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

Server operating systems

All OS with a Java VM

Linux

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

the object must implement a serialization strategy

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

JCache
JPA
RESTful HTTP API

proprietary protocol using JSON

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

.Net
C++
Java

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

JavaScript

Triggers

yes

Events

yes

Live Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

yes, with selectable consistency level

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

one or two-phase-commit; repeatable reads; read commited

configurable

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

optionally

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

via In-Memory Engine

yes

User concepts

Access control

Role-based access control

authentification to access the cache via certificates or http basic authentication

Access rights for users and roles

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.