DBMS > Axibase vs. EJDB vs. Google Cloud Datastore vs. Hazelcast vs. SQLite

System Properties Comparison Axibase vs. EJDB vs. Google Cloud Datastore vs. Hazelcast vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A widely adopted in-memory data grid

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	0.35
Rank	#282	Overall
	#25	Time Series DBMS

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	4.36
Rank	#72	Overall
	#12	Document stores

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

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

axibase.com/docs/atsd/finance

github.com/Softmotions/ejdb

cloud.google.com/datastore

hazelcast.com

www.sqlite.org

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

cloud.google.com/datastore/docs

hazelcast.org/imdg/docs

www.sqlite.org/docs.html

Developer

Axibase Corporation

Softmotions

Google

Hazelcast

Dwayne Richard Hipp

Initial release

2013

2012

2008

2000

Current release

15585

5.3.6, November 2023

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

Open Source

GPLv2

commercial

Open Source

Apache Version 2; commercial licenses available

Open Source

Public Domain

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

Server operating systems

Linux

server-less

hosted

All OS with a Java VM

server-less

Data scheme

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

yes

string, integer, double, bool, date, object_id

yes, details here

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

SQL-like query language (GQL)

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

in-process shared library

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JCache
JPA
Memcached protocol
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Go
Java
PHP
Python
R
Ruby

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

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

using Google App Engine

yes

Event Listeners, Executor Services

Triggers

yes

Callbacks using the Google Apps Engine

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Multi-source replication using Paxos

yes

Replicated Map

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

via file-system locks

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

User concepts

Access control

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Role-based access control

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.