DBMS > FatDB vs. GeoMesa vs. Google Cloud Spanner vs. LokiJS

System Properties Comparison FatDB vs. GeoMesa vs. Google Cloud Spanner vs. LokiJS

Please select another system to include it in the comparison.

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.

Description

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

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

A horizontally scalable, globally consistent, relational database service. It is the externalization of the core Google database that runs the biggest aspects of Google, like Ads and Google Play.

In-memory JavaScript DBMS

Primary database model

Document store
Key-value store

Spatial DBMS

Relational DBMS

Document store

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	2.84
Rank	#100	Overall
	#51	Relational DBMS

Score	0.49
Rank	#260	Overall
	#42	Document stores

Website

www.geomesa.org

cloud.google.com/spanner

github.com/techfort/LokiJS

Technical documentation

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

cloud.google.com/spanner/docs

techfort.github.io/LokiJS

Developer

FatCloud

CCRi and others

Google

Initial release

2012

2014

2017

2014

Current release

5.0.0, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

Open Source

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

Scala

JavaScript

Server operating systems

Windows

hosted

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

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

via views

SQL

Support of SQL

Via inetgration in SQL Server

yes

Query statements complying to ANSI 2011

APIs and other access methods

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

gRPC (using protocol buffers) API
JDBC

At present, JDBC supports read-only queries. No support for DDL or DML statements.
RESTful HTTP API

JavaScript API

Supported programming languages

Go
Java
JavaScript (Node.js)
Python

JavaScript

Server-side scripts

Stored procedures

yes

via applications

View functions in JavaScript

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

depending on storage layer

Multi-source replication with 3 replicas for regional instances.

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

depending on storage layer

Immediate Consistency

none

Foreign keys

Referential integrity

yes

by using interleaved tables, this features focuses more on performance improvements than on referential integrity

Transaction concepts

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

ACID

Strict serializable isolation

atomic operations within a single collection possible

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

Can implement custom security layer via applications

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

New kids on the block: database management systems implemented in JavaScript
1 December 2014, Matthias Gelbmann

show all

Recent citations in the news

Google's Cloud Spanner Now Spans Continents … Like It's Supposed to Do
31 May 2024, Data Center Knowledge

Google Improves Cloud Spanner: More Compute and Storage without Price Increase
14 October 2023, InfoQ.com

Google makes its Cloud Spanner database service faster and more cost-efficient
11 October 2023, SiliconANGLE News

Google turns up the heat on AWS, claims Cloud Spanner is half the cost of DynamoDB
11 October 2023, TechCrunch

Google Spanner: When Do You Need to Move to It?
11 September 2023, hackernoon.com

provided by Google News

LokiJS - A JavaScript Database
18 November 2014, iProgrammer

provided by Google News

Share this page