DBMS > AgensGraph vs. Amazon CloudSearch vs. Firebase Realtime Database vs. OrigoDB vs. SQLite

System Properties Comparison AgensGraph vs. Amazon CloudSearch vs. Firebase Realtime Database vs. OrigoDB vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

A hosted search engine service by Amazon with the data stored in Amazons cloud

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

A fully ACID in-memory object graph database

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS
Relational DBMS

Search engine

Document store

Document store
Object oriented DBMS

Relational DBMS

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

Score	0.20
Rank	#321	Overall
	#27	Graph DBMS
	#143	Relational DBMS

Score	1.85
Rank	#137	Overall
	#12	Search engines

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

bitnine.net/agensgraph

aws.amazon.com/cloudsearch

firebase.google.com/products/realtime-database

origodb.com

www.sqlite.org

Technical documentation

bitnine.net/documentation

docs.aws.amazon.com/cloudsearch

firebase.google.com/docs/database

origodb.com/docs

www.sqlite.org/docs.html

Developer

Bitnine Global Inc.

Amazon

Google

acquired by Google 2014

Robert Friberg et al

Dwayne Richard Hipp

Initial release

2016

2012

2009

under the name LiveDB

2000

Current release

2.1, December 2018

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

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

Server operating systems

Linux
OS X
Windows

hosted

Linux
Windows

server-less

Data scheme

depending on used data model

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

all search fields are automatically indexed

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

Cypher Query Language
JDBC

HTTP API

Android
iOS
JavaScript API
RESTful HTTP API

.NET Client API
HTTP API
LINQ

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
Java
JavaScript
Python

Java
JavaScript
Objective-C

.Net

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

limited functionality with using 'rules'

yes

Triggers

Callbacks are triggered when data changes

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

yes

automatic partitioning across Amazon Search Instance as required

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes

managed transparently by AWS

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

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

Foreign keys

Referential integrity

yes

depending on model

yes

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

Write ahead log

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

fine grained access rights according to SQL-standard

authentication via encrypted signatures

yes, based on authentication and database rules

Role based authorization

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.