DBMS > BigObject vs. GeoMesa vs. OrigoDB vs. RavenDB

System Properties Comparison BigObject vs. GeoMesa vs. OrigoDB vs. RavenDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

A fully ACID in-memory object graph database

Open Source Operational and Transactional Enterprise NoSQL Document Database

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Spatial DBMS

Document store
Object oriented DBMS

Document store

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

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

Score	2.92
Rank	#101	Overall
	#18	Document stores

Website

Technical documentation

docs.bigobject.io

www.geomesa.org/documentation/stable/user/index.html

origodb.com/docs

ravendb.net/docs

Developer

BigObject, Inc.

CCRi and others

Robert Friberg et al

Hibernating Rhinos

Initial release

2015

2014

2009

under the name LiveDB

2010

Current release

4.0.5, February 2024

5.4, July 2022

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache License 2.0

Open Source

AGPL version 3, commercial license available

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

Scala

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Data scheme

yes

schema-free

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

SQL-like DML and DDL statements

SQL-like query language (RQL)

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

.NET Client API
HTTP API
LINQ

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

Supported programming languages

.Net

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

Server-side scripts

Stored procedures

Lua

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

horizontal partitioning

client side managed; servers are not synchronized

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

depending on storage layer

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

depending on model

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

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

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Role based authorization

Authorization levels configured per client 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.

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

RavenDB Welcomes David Baruc as Chief Revenue Officer: Seasoned Tech Leader to Drive Global Sales and ...
13 June 2023, PR Newswire

Install the NoSQL RavenDB Data System
14 May 2021, The New Stack

Oren Eini on RavenDB, Including Consistency Guarantees and C# as the Implementation Language
23 May 2022, InfoQ.com

RavenDB Adds Graph Queries
15 May 2019, Datanami

How I Created a RavenDB Python Client
23 September 2016, Visual Studio Magazine

provided by Google News

Share this page