DBMS > FatDB vs. InfinityDB vs. Machbase Neo vs. SpaceTime vs. Yaacomo

System Properties Comparison FatDB vs. InfinityDB vs. Machbase Neo vs. SpaceTime vs. Yaacomo

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

TimeSeries DBMS for AIoT and BigData

SpaceTime is a spatio-temporal DBMS with a focus on performance.

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store
Key-value store

Secondary database models

Relational DBMS

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

Score	0.08
Rank	#365	Overall
	#55	Key-value stores

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	0.03
Rank	#392	Overall
	#8	Spatial DBMS

Website

boilerbay.com

machbase.com

www.mireo.com/spacetime

yaacomo.com

Technical documentation

boilerbay.com/infinitydb/manual

machbase.com/dbms

Developer

FatCloud

Boiler Bay Inc.

Machbase

Mireo

Q2WEB GmbH

Initial release

2012

2002

2013

2020

2009

Current release

4.0

V8.0, August 2023

License

Commercial or Open Source

commercial

free test version available

commercial

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

Java

C++

Server operating systems

Windows

All OS with a Java VM

Linux
macOS
Windows

Linux

Android
Linux
Windows

Data scheme

schema-free

yes

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

yes

Typing

predefined data types such as float or date

yes

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

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.

Secondary indexes

yes

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

yes

SQL

Support of SQL

Via inetgration in SQL Server

SQL-like query language

A subset of ANSI SQL is implemented

yes

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

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

RESTful HTTP API

JDBC
ODBC

Supported programming languages

Java

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

C#
C++
Python

Server-side scripts

Stored procedures

yes

via applications

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Fixed-grid hypercubes

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

selectable replication factor

Real-time block device replication (DRBD)

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

READ-COMMITTED or SERIALIZED

Immediate Consistency

Foreign keys

Referential integrity

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

yes

Transaction concepts

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

ACID

Optimistic locking for transactions; no isolation for bulk loads

ACID

Concurrency

Support for concurrent manipulation of data

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.

yes

volatile and lookup table

yes

User concepts

Access control

Can implement custom security layer via applications

simple password-based access control

yes

fine grained access rights according to SQL-standard

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.

Share this page