DBMS > Bangdb vs. GeoMesa vs. Google Cloud Datastore vs. STSdb

System Properties Comparison Bangdb vs. GeoMesa vs. Google Cloud Datastore vs. STSdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Converged and high performance database for device data, events, time series, document and graph

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store
Graph DBMS
Time Series DBMS

Spatial DBMS

Document store

Key-value store

Secondary database models

Spatial DBMS

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

Score	0.07
Rank	#346	Overall
	#47	Document stores
	#35	Graph DBMS
	#32	Time Series DBMS

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	0.03
Rank	#365	Overall
	#54	Key-value stores

Website

bangdb.com

www.geomesa.org

cloud.google.com/datastore

github.com/STSSoft/STSdb4

Technical documentation

docs.bangdb.com

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

cloud.google.com/datastore/docs

Developer

Sachin Sinha, BangDB

CCRi and others

Google

STS Soft SC

Initial release

2012

2014

2008

2011

Current release

BangDB 2.0, October 2021

5.0.1, July 2024

4.0.8, September 2015

License

Commercial or Open Source

Open Source

BSD 3

Open Source

Apache License 2.0

commercial

Open Source

GPLv2, commercial license 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

C, C++

Scala

Server operating systems

Linux

hosted

Windows

Data scheme

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes: string, long, double, int, geospatial, stream, events

yes

yes, details here

yes

primitive types and user defined types (classes)

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

secondary, composite, nested, reverse, geospatial

yes

SQL

Support of SQL

SQL like support with command line tool

SQL-like query language (GQL)

APIs and other access methods

Proprietary protocol
RESTful HTTP API

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

.NET Client API

Supported programming languages

C
C#
C++
Java
Python

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

C#
Java

Server-side scripts

Stored procedures

using Google App Engine

Triggers

yes, Notifications (with Streaming only)

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding (enterprise version only). P2P based virtual network overlay with consistent hashing and chord algorithm

depending on storage layer

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor, Knob for CAP (enterprise version only)

depending on storage layer

Multi-source replication using Paxos

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable consistency, set CAP knob accordingly

depending on storage layer

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

Concurrency

Support for concurrent manipulation of data

yes, optimistic concurrency control

yes

Durability

Support for making data persistent

yes, implements WAL (Write ahead log) as well

yes

In-memory capabilities

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

yes, run db with in-memory only mode

depending on storage layer

User concepts

Access control

yes (enterprise version only)

yes

depending on the DBMS used for storage

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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

Google Cloud vs AWS: Which Cloud Computing Platform is Better?
11 September 2024, Cloudwards

Google Gets Rid of Fees To Transfer Data Out of Cloud Platform
12 January 2024, Spiceworks News and Insights

Best cloud storage of 2024
13 September 2024, TechRadar

What Is Google Cloud? Platform, Benefits & More Explained
11 September 2024, Cloudwards

Google App Engine
26 April 2024, TechTarget

provided by Google News

Share this page