DBMS > Hazelcast vs. Lovefield vs. Postgres-XL vs. TerarkDB

System Properties Comparison Hazelcast vs. Lovefield vs. Postgres-XL vs. TerarkDB

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

Embeddable relational database for web apps written in pure JavaScript

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Key-value store

Relational DBMS

Key-value store

Secondary database models

Document store

JSON support with IMDG 3.12

Document store
Spatial DBMS

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

Score	5.97
Rank	#57	Overall
	#6	Key-value stores

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

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

Website

hazelcast.com

google.github.io/lovefield

www.postgres-xl.org

github.com/bytedance/terarkdb

Technical documentation

hazelcast.org/imdg/docs

github.com/google/lovefield/blob/master/docs/spec_index.md

www.postgres-xl.org/documentation

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

Hazelcast

Google

ByteDance, originally Terark

Initial release

2008

2014

since 2012, originally named StormDB

2016

Current release

5.3.6, November 2023

2.1.12, February 2017

10 R1, October 2018

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

Open Source

Mozilla public license

commercial

restricted open source version 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

JavaScript

C++

Server operating systems

All OS with a Java VM

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux
macOS

Data scheme

schema-free

yes

schema-free

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

the object must implement a serialization strategy

yes

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

yes

distributed, parallel query execution

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

C++ API
Java API

Supported programming languages

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

JavaScript

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C++
Java

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

user defined functions

Triggers

yes

Events

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

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

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

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

yes

User concepts

Access control

Role-based access control

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Hazelcast Weaves Wider Logic Threads Through The Data Fabric
7 March 2024, Forbes

Hazelcast 5.4 real time data processing platform boosts AI and consistency
17 April 2024, VentureBeat

Hazelcast Sets New Standards for AI Workloads with Platform 5.4 Enhancements
18 April 2024, Datanami

Research Report on Event Stream Processing Tools Market Size 2024-2030: Supply-Demand Trends, Regional ...
3 May 2024, NEWS CHANNEL NEBRASKA

Real-Time Data Platform Hazelcast Introduces New Chief Technology Officer Adrian Soars
7 November 2023, Finovate

provided by Google News

Share this page