DBMS > GeoMesa vs. Lovefield vs. Microsoft Access vs. Snowflake vs. TigerGraph

System Properties Comparison GeoMesa vs. Lovefield vs. Microsoft Access vs. Snowflake vs. TigerGraph

Editorial information provided by DB-Engines

Name

Description

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

Embeddable relational database for web apps written in pure JavaScript

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Cloud-based data warehousing service for structured and semi-structured data

A complete, distributed, parallel graph computing platform supporting web-scale data analytics in real-time

Primary database model

Spatial DBMS

Relational DBMS

Graph DBMS

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	1.80
Rank	#138	Overall
	#13	Graph DBMS

Website

www.geomesa.org

google.github.io/lovefield

www.microsoft.com/en-us/microsoft-365/access

www.snowflake.com

www.tigergraph.com

Technical documentation

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

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

developer.microsoft.com/en-us/access

docs.snowflake.net/manuals/index.html

docs.tigergraph.com

Developer

CCRi and others

Google

Microsoft

Snowflake Computing Inc.

Initial release

2014

1992

2014

2017

Current release

5.0.0, May 2024

2.1.12, February 2017

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

commercial

Bundled with Microsoft Office

commercial

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

C++

Server operating systems

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

tested with Chrome, Firefox, IE, Safari

Windows

Not a real database server, but making use of DLLs

hosted

Linux

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

yes

but not compliant to any SQL standard

yes

SQL-like query language (GSQL)

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

CLI Client
JDBC
ODBC

GSQL (TigerGraph Query Language)
Kafka
RESTful HTTP/JSON API

Supported programming languages

JavaScript

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

JavaScript (Node.js)
Python

C++
Java

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

user defined functions

yes

Triggers

Using read-only observers

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

but no files for transaction logging

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

but no files for transaction logging

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

User concepts

Access control

yes

depending on the DBMS used for storage

a simple user-level security was built in till version Access 2003

Users with fine-grained authorization concept, user roles and pluggable authentication

Role-based access control

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.