DBMS > AgensGraph vs. EventStoreDB vs. Firebase Realtime Database vs. Machbase Neo vs. OrigoDB

System Properties Comparison AgensGraph vs. EventStoreDB vs. Firebase Realtime Database vs. Machbase Neo vs. OrigoDB

Editorial information provided by DB-Engines

Name

Description

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

Industrial-strength, open-source database solution built from the ground up for event sourcing.

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

TimeSeries DBMS for AIoT and BigData

A fully ACID in-memory object graph database

Primary database model

Graph DBMS
Relational DBMS

Event Store

Document store

Time Series DBMS

Document store
Object oriented DBMS

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

Score	0.18
Rank	#315	Overall
	#28	Graph DBMS
	#141	Relational DBMS

Score	1.07
Rank	#175	Overall
	#1	Event Stores

Score	13.43
Rank	#39	Overall
	#6	Document stores

Score	0.06
Rank	#352	Overall
	#33	Time Series DBMS

Score	0.00
Rank	#386	Overall
	#54	Document stores
	#20	Object oriented DBMS

Website

bitnine.net/agensgraph

www.eventstore.com

firebase.google.com/products/realtime-database

machbase.com

origodb.com

Technical documentation

bitnine.net/documentation

developers.eventstore.com

firebase.google.com/docs/database

machbase.com/dbms

origodb.com/docs

Developer

Bitnine Global Inc.

Event Store Limited

Google

acquired by Google 2014

Machbase

Robert Friberg et al

Initial release

2016

2012

2013

2009

under the name LiveDB

Current release

2.1, December 2018

21.2, February 2021

V8.0, August 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

commercial

free test version available

Open Source

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

Linux
Windows

hosted

Linux
macOS
Windows

Linux
Windows

Data scheme

depending on used data model

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

Cypher Query Language
JDBC

Android
iOS
JavaScript API
RESTful HTTP API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

.NET Client API
HTTP API
LINQ

Supported programming languages

C
Java
JavaScript
Python

Java
JavaScript
Objective-C

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

.Net

Server-side scripts

Stored procedures

yes

limited functionality with using 'rules'

yes

Triggers

Callbacks are triggered when data changes

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

selectable replication factor

Source-replica replication

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

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

In-memory capabilities

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

yes

volatile and lookup table

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes, based on authentication and database rules

simple password-based access control

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.

Related products and services

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

More resources

DB-Engines blog posts

Cloud-based DBMS's popularity grows at high rates
12 December 2019, Paul Andlinger

show all

Recent citations in the news

Graph DBMS Performance Comparison AgensGraph vs. Neo4j
29 June 2017, Business Wire

Bitnine Releases AgensGraph 2.1, the Multi-model Graph Database Optimized for the Legacy Environment
29 January 2019, Business Wire

Bitnine: The Newly Revealed ‘AI Teacher’ Powered by Graph Database Delivers Hyper-Personalized Learning Experience
25 March 2019, Business Wire

provided by Google News

Instant harkens back to a pre-Google Firebase
2 October 2024, TechCrunch

Supabase vs. Firebase: Which BaaS is Best for Your App?
14 August 2024, Netguru

Misconfigured Firebase instances leaked 19 million plaintext passwords
19 March 2024, BleepingComputer

Don't be like these 900+ websites and expose millions of passwords via Firebase
18 March 2024, The Register

Google Cloud beefs up database services for generative AI workloads
2 October 2024, SiliconANGLE News

provided by Google News

Share this page