DBMS > FatDB vs. GeoSpock vs. Immudb vs. JaguarDB vs. Lovefield

System Properties Comparison FatDB vs. GeoSpock vs. Immudb vs. JaguarDB vs. Lovefield

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

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

Performant, highly scalable DBMS for AI and IoT applications

Embeddable relational database for web apps written in pure JavaScript

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

Key-value store
Vector DBMS

Relational DBMS

Secondary database models

Time Series DBMS

Relational DBMS

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

Score	0.24
Rank	#305	Overall
	#43	Key-value stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Website

geospock.com

github.com/codenotary/immudb
immudb.io

www.jaguardb.com

google.github.io/lovefield

Technical documentation

docs.immudb.io

www.jaguardb.com/support.html

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

Developer

FatCloud

GeoSpock

Codenotary

DataJaguar, Inc.

Google

Initial release

2012

2020

2015

2014

Current release

2.0, September 2019

1.2.3, April 2022

3.3 July 2023

2.1.12, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

GPL V3.0

Open Source

Apache 2.0

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

C++

the server part. Clients available in other languages

JavaScript

Server operating systems

Windows

hosted

BSD
Linux
macOS
Solaris
Windows
z/OS

Linux

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

tested with Chrome, Firefox, IE, Safari

Data scheme

schema-free

yes

schema-free

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.

Secondary indexes

yes

temporal, categorical

yes

SQL

Support of SQL

Via inetgration in SQL Server

ANSI SQL for query only (using Presto)

SQL-like syntax

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

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

gRPC protocol
PostgreSQL wire protocol

JDBC
ODBC

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
Python

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

JavaScript

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

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

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

Eventual 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

In-memory capabilities

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

yes

using MemoryDB

User concepts

Access control

Can implement custom security layer via applications

Access rights for users can be defined per table

rights management via user accounts

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

Recent citations in the news

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

Imagining an 'Everything Connected' World With Geospock | AWS Startups Blog
20 June 2019, AWS Blog

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

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

Codenotary Releases immudb v1.9DOM
19 October 2023, businesswire.com

Codenotary brings its immutable database to the cloud
21 June 2023, TechCrunch

Codenotary launches cloud version of tamper-proof database
27 June 2023, SC Media

ImmuDB and Codenotary: It's a database, but the company isn't
20 December 2021, ZDNet

Immudb: Open-source database, built on a zero trust model
17 December 2021, Help Net Security

provided by Google News

Share this page