DBMS > Brytlyt vs. GeoMesa vs. IBM Cloudant vs. InfinityDB

System Properties Comparison Brytlyt vs. GeoMesa vs. IBM Cloudant vs. InfinityDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

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

Database as a Service offering based on Apache CouchDB

A Java embedded Key-Value Store which extends the Java Map interface

Primary database model

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

Score	0.27
Rank	#292	Overall
	#132	Relational DBMS

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	2.85
Rank	#95	Overall
	#18	Document stores

Score	0.00
Rank	#383	Overall
	#59	Key-value stores

Website

brytlyt.io

www.geomesa.org

www.ibm.com/products/cloudant

boilerbay.com

Technical documentation

docs.brytlyt.io

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

cloud.ibm.com/docs/Cloudant

boilerbay.com/infinitydb/manual

Developer

Brytlyt

CCRi and others

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Boiler Bay Inc.

Initial release

2016

2014

2010

2002

Current release

5.0, August 2023

5.0.1, July 2024

4.0

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

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++ and CUDA

Scala

Erlang

Java

Server operating systems

Linux
OS X
Windows

hosted

All OS with a Java VM

Data scheme

yes

schema-free

yes

nested virtual Java Maps, multi-value, logical â€˜tuple spaceâ€™ runtime Schema upgrade

Typing

predefined data types such as float or date

yes

all Java primitives, Date, CLOB, BLOB, huge sparse arrays

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

manual creation possible, using inversions based on multi-value capability

SQL

Support of SQL

yes

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

RESTful HTTP/JSON API

Access via java.util.concurrent.ConcurrentNavigableMap Interface
Proprietary API to InfinityDB ItemSpace (boilerbay.com/docs/ItemSpaceDataStructures.htm)

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C#
Java
JavaScript
Objective-C
PHP
Ruby

Java

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

View functions (Map-Reduce) in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

depending on storage layer

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Eventual Consistency

Immediate Consistency

READ-COMMITTED or SERIALIZED

Foreign keys

Referential integrity

yes

manual creation possible, using inversions based on multi-value capability

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

Optimistic locking for transactions; no isolation for bulk loads

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

In-memory capabilities

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

depending on storage layer

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

Access rights for users can be defined 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

Opensignal Announces Acquisition of Brytlyt GPU-based Data Analytics & Visualization Technology
5 June 2024, PR Web

Brytlyt releases version 5.0, introducing a more intuitive, intelligent and flexible analytics platform
1 August 2023, PR Newswire

Bringing GPUs To Bear On Bog Standard Relational Databases
26 February 2018, The Next Platform

London’s Brytlyt raises €4.4 million for its data analytics and visualisation technology
22 December 2021, EU-Startups

Future of Data Visualization and Agile Business Intelligence
17 May 2021, insideHPC

provided by Google News

Cloudant Best (and Worst) Practices — Part 1
18 March 2019, IBM

Intro to Enterprise Cloud Storage: How to Set Up a Cloudant Database
1 December 2014, Linux.com

IBM to Purchase Cloudant Database as a service (DBaaS) Provider
22 March 2014, App Developer Magazine

IBM Code Engine and IBM Cloudant: Serverless Data and Infrastructure
16 August 2021, IBM

From Cloud Foundry to Code Engine: Service Bindings and Code
15 March 2022, IBM

provided by Google News

Share this page