DBMS > Amazon Neptune vs. Firebase Realtime Database vs. GridDB vs. SQLite vs. Ultipa

System Properties Comparison Amazon Neptune vs. Firebase Realtime Database vs. GridDB vs. SQLite vs. Ultipa

Editorial information provided by DB-Engines

Name

Description

Fast, reliable graph database built for the cloud

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Scalable in-memory time series database optimized for IoT and Big Data

Widely used embeddable, in-process RDBMS

High performance Graph DBMS supporting HTAP high availability cluster deployment

Primary database model

Secondary database models

Key-value store
Relational DBMS

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

Score	2.20
Rank	#113	Overall
	#9	Graph DBMS
	#5	RDF stores

Score	13.60
Rank	#39	Overall
	#6	Document stores

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	0.11
Rank	#338	Overall
	#32	Graph DBMS

Website

aws.amazon.com/neptune

firebase.google.com/products/realtime-database

griddb.net

www.sqlite.org

www.ultipa.com

Technical documentation

aws.amazon.com/neptune/developer-resources

firebase.google.com/docs/database

docs.griddb.net

www.sqlite.org/docs.html

www.ultipa.com/document

Developer

Amazon

Google

acquired by Google 2014

Toshiba Corporation

Dwayne Richard Hipp

Ultipa

Initial release

2017

2012

2013

2000

2019

Current release

5.1, August 2022

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

Open Source

Public Domain

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

C++

Server operating systems

hosted

Linux

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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.

Secondary indexes

yes

SQL

Support of SQL

SQL92, SQL-like TQL (Toshiba Query Language)

yes

SQL-92 is not fully supported

APIs and other access methods

OpenCypher
RDF 1.1 / SPARQL 1.1
TinkerPop Gremlin

Android
iOS
JavaScript API
RESTful HTTP API

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

RESTful HTTP API

Supported programming languages

C#
Go
Java
JavaScript
PHP
Python
Ruby
Scala

Java
JavaScript
Objective-C

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

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

C++
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

limited functionality with using 'rules'

Triggers

Callbacks are triggered when data changes

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones high availability, asynchronous replication for up to 15 read replicas within a single region. Global database clusters consists of a primary write DB cluster in one region, and up to five secondary read DB clusters in different regions. Each secondary region can have up to 16 reader instances.

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate consistency within container, eventual consistency across containers

Foreign keys

Referential integrity

yes

Relationships in graphs

yes

Transaction concepts

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

ACID

yes

ACID at container level

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

with encyption-at-rest

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 and roles can be defined via the AWS Identity and Access Management (IAM)

yes, based on authentication and database rules

Access rights for users can be defined per database

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.