DBMS > Graph Engine vs. Ignite vs. JSqlDb vs. PostGIS vs. SQLite

System Properties Comparison Graph Engine vs. Ignite vs. JSqlDb vs. PostGIS vs. SQLite

Editorial information provided by DB-Engines

Name

JSqlDB seems to be discontinued. Therefore it is excluded from the DB-Engines ranking.

Description

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

JavaScript Query Language Database, stores JavaScript objects and primitives

Spatial extension of PostgreSQL

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS
Key-value store

Key-value store
Relational DBMS

Document store
Object oriented DBMS

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	0.61
Rank	#240	Overall
	#21	Graph DBMS
	#35	Key-value stores

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

jsqldb.org (offline)

Technical documentation

www.graphengine.io/docs/manual

apacheignite.readme.io/docs

postgis.net/documentation

www.sqlite.org/docs.html

Developer

Microsoft

Apache Software Foundation

Konrad von Backstrom

Dwayne Richard Hipp

Initial release

2010

2015

2018

2005

2000

Current release

Apache Ignite 2.6

0.8, December 2018

3.4.2, February 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

MIT License

Open Source

Apache 2.0

Open Source

GPL v2.0

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

.NET and C

C++, Java, .Net

Server operating systems

.NET

Linux
OS X
Solaris
Windows

Linux
macOS
Windows

server-less

Data scheme

yes

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

Secondary indexes

yes

SQL

Support of SQL

ANSI-99 for query and DML statements, subset of DDL

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
C++
F#
Visual Basic

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript

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

yes (compute grid and cache interceptors can be used instead)

functions in JavaScript

user defined functions

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning

Sharding

none

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

none

yes

based on PostgreSQL

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

using RocksDB

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

Security Hooks for custom implementations

yes

based on PostgreSQL

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.