DBMS > BigObject vs. GeoMesa vs. Realm vs. Snowflake vs. Sphinx

System Properties Comparison BigObject vs. GeoMesa vs. Realm vs. Snowflake vs. Sphinx

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 DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Cloud-based data warehousing service for structured and semi-structured data

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

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	7.60
Rank	#52	Overall
	#9	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

Technical documentation

docs.bigobject.io

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

realm.io/docs

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

Developer

BigObject, Inc.

CCRi and others

Realm, acquired by MongoDB in May 2019

Snowflake Computing Inc.

Sphinx Technologies Inc.

Initial release

2015

2014

2001

Current release

4.0.5, February 2024

3.5.1, February 2023

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache License 2.0

Open Source

commercial

Open Source

GPL version 2, commercial licence available

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

Scala

C++

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Android
Backend: server-less
iOS
Windows

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

yes

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

full-text index on all search fields

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-like query language (SphinxQL)

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

CLI Client
JDBC
ODBC

Proprietary protocol

Supported programming languages

.Net
Java

with Android only
Objective-C
React Native
Swift

JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

Lua

runs within the applications so server-side scripts are unnecessary

user defined functions

Triggers

yes

Change Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

none

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

none

yes

none

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

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

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

In-Memory realm

User concepts

Access control

yes

depending on the DBMS used for storage

yes

Users with fine-grained authorization concept, user roles and pluggable authentication

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.