DBMS > GeoMesa vs. Google Cloud Spanner vs. Lovefield vs. SQLite

System Properties Comparison GeoMesa vs. Google Cloud Spanner vs. Lovefield vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

Embeddable relational database for web apps written in pure JavaScript

Widely used embeddable, in-process RDBMS

Primary database model

Spatial DBMS

Relational DBMS

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.33
Rank	#286	Overall
	#131	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

www.geomesa.org

cloud.google.com/spanner

google.github.io/lovefield

www.sqlite.org

Technical documentation

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

cloud.google.com/spanner/docs

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

www.sqlite.org/docs.html

Developer

CCRi and others

Google

Dwayne Richard Hipp

Initial release

2014

2017

2014

2000

Current release

5.0.0, May 2024

2.1.12, February 2017

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Apache 2.0

Open Source

Public Domain

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

hosted

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

tested with Chrome, Firefox, IE, Safari

server-less

Data scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL

Support of SQL

yes

Query statements complying to ANSI 2011

SQL-like query language

via JavaScript builder pattern

yes

SQL-92 is not fully supported

APIs and other access methods

gRPC (using protocol buffers) API
JDBC

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Go
Java
JavaScript (Node.js)
Python

JavaScript

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

Triggers

Using read-only observers

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

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

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

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

yes

Transaction concepts

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

ACID

Strict serializable isolation

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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.

depending on storage layer

yes

using MemoryDB

yes

User concepts

Access control

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.