DBMS > GeoMesa vs. Microsoft Access vs. SiteWhere vs. Snowflake vs. SpaceTime

System Properties Comparison GeoMesa vs. Microsoft Access vs. SiteWhere vs. Snowflake vs. SpaceTime

Editorial information provided by DB-Engines

Name

Description

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

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.)

M2M integration platform for persisting/querying time series data

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

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Secondary database models

Relational DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Website

www.geomesa.org

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

github.com/sitewhere/sitewhere

www.snowflake.com

www.mireo.com/spacetime

Technical documentation

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

developer.microsoft.com/en-us/access

sitewhere1.sitewhere.io/index.html

docs.snowflake.net/manuals/index.html

Developer

CCRi and others

Microsoft

SiteWhere

Snowflake Computing Inc.

Mireo

Initial release

2014

1992

2010

2014

2020

Current release

5.0.0, May 2024

1902 (16.0.11328.20222), March 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Bundled with Microsoft Office

Open Source

Common Public Attribution License Version 1.0

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

C++

Java

C++

Server operating systems

Windows

Not a real database server, but making use of DLLs

Linux
OS X
Windows

hosted

Linux

Data scheme

yes

predefined 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

yes

but not compliant to any SQL standard

yes

A subset of ANSI SQL is implemented

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

HTTP REST

CLI Client
JDBC
ODBC

RESTful HTTP API

Supported programming languages

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

JavaScript (Node.js)
Python

C#
C++
Python

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

user defined functions

Triggers

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

Sharding

based on HBase

yes

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

selectable replication factor

based on HBase

yes

Real-time block device replication (DRBD)

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

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

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

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

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

yes

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.