DBMS > FatDB vs. GeoSpock vs. Lovefield vs. ObjectBox vs. TerarkDB

System Properties Comparison FatDB vs. GeoSpock vs. Lovefield vs. ObjectBox vs. TerarkDB

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.

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

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

Spatial and temporal data processing engine for extreme data scale

Embeddable relational database for web apps written in pure JavaScript

Extremely fast embedded database for small devices, IoT and Mobile

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Primary database model

Document store
Key-value store

Relational DBMS

Object oriented DBMS

Key-value store

Secondary database models

Time Series DBMS

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

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	1.20
Rank	#170	Overall
	#5	Object oriented DBMS

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

Website

geospock.com

google.github.io/lovefield

objectbox.io

github.com/bytedance/terarkdb

Technical documentation

github.com/google/lovefield/blob/master/docs/spec_index.md

docs.objectbox.io

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

Developer

FatCloud

GeoSpock

Google

ObjectBox Limited

ByteDance, originally Terark

Initial release

2012

2014

2017

2016

Current release

2.0, September 2019

2.1.12, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache License 2.0

commercial

restricted open source version 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

Java, Javascript

JavaScript

C and C++

C++

Server operating systems

Windows

hosted

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Android
iOS
Linux
macOS
Windows

Data scheme

schema-free

yes

schema-free

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.

Secondary indexes

yes

temporal, categorical

yes

SQL

Support of SQL

Via inetgration in SQL Server

ANSI SQL for query only (using Presto)

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

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

JDBC

Proprietary native API

C++ API
Java API

Supported programming languages

JavaScript

C
C++
Dart
Go
Java
JavaScript

planned (as of Jan 2019)
Kotlin
Python

planned (as of Jan 2019)
Swift

C++
Java

Server-side scripts

Stored procedures

yes

via applications

Triggers

yes

via applications

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

online/offline synchronization between client and server

none

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

yes

User concepts

Access control

Can implement custom security layer via applications

Access rights for users can be defined per table

yes

More information provided by the system vendor

News

Evolution of search: traditional vs vector search
23 May 2024

On-device Vector Database for Dart/Flutter
21 May 2024

The first On-Device Vector Database: ObjectBox 4.0
16 May 2024

SQLite and SQLite alternatives – a comprehensive overview
7 May 2024

Edge AI: The era of on-device AI
23 April 2024

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

Recent citations in the news

How GeoSpock is supercharging geospatial analytics
23 February 2021, ComputerWeekly.com

GeoSpock launches Spatial Big Data Platform 2.0
4 September 2019, VanillaPlus

Cambridge-based data analytics startup GeoSpock lands €4.6 million
2 October 2020, EU-Startups

nChain Leads Investment Round in Extreme-scale Data Firm GeoSpock
2 October 2020, AlexaBlockchain

Smart Cities, Autonomous Vehicles, Artificial General Intelligence Robotics: Q&A with Steve Marsh, GeoSpock
16 May 2018, ExchangeWire

provided by Google News

Industrial IoT (IIoT) edge solution for railway operators – a Kapsch ObjectBox Case Study
21 June 2019, 1E9

The Megashift Towards Decentralized Edge Computing
27 August 2021, hackernoon.com

provided by Google News

Share this page