DBMS > GeoMesa vs. Microsoft Access vs. Microsoft Azure AI Search vs. Oracle vs. Tarantool

System Properties Comparison GeoMesa vs. Microsoft Access vs. Microsoft Azure AI Search vs. Oracle vs. Tarantool

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

Search-as-a-service for web and mobile app development

Widely used RDBMS

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Document store
Key-value store
Relational DBMS

Secondary database models

Vector DBMS

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

Spatial DBMS

with Tarantool/GIS extension

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	5.52
Rank	#59	Overall
	#6	Search engines

Score	1244.08
Rank	#1	Overall
	#1	Relational DBMS

Score	1.67
Rank	#143	Overall
	#25	Document stores
	#25	Key-value stores
	#65	Relational DBMS

Website

www.geomesa.org

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

azure.microsoft.com/en-us/services/search

www.oracle.com/database

www.tarantool.io

Technical documentation

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

developer.microsoft.com/en-us/access

learn.microsoft.com/en-us/azure/search

docs.oracle.com/en/database

www.tarantool.io/en/doc

Developer

CCRi and others

Microsoft

Oracle

Initial release

2014

1992

2015

1980

2008

Current release

5.0.0, May 2024

1902 (16.0.11328.20222), March 2019

23c, September 2023

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Bundled with Microsoft Office

commercial

restricted free version is available

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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++

C and C++

Server operating systems

Windows

Not a real database server, but making use of DLLs

hosted

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

BSD
Linux
macOS

Data scheme

yes

Schemaless in JSON and XML columns

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

with proprietary extensions

Full-featured ANSI SQL support

APIs and other access methods

ADO.NET
DAO
ODBC
OLE DB

RESTful HTTP API

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Open binary protocol

Supported programming languages

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

C#
Java
JavaScript
Python

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

PL/SQL

also stored procedures in Java possible

Lua, C and SQL stored procedures

Triggers

yes

since Access 2010 using the ACE-engine

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

Implicit feature of the cloud service

Sharding, horizontal partitioning

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

yes

Implicit feature of the cloud service

Multi-source replication
Source-replica replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

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

isolation level can be parameterized

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

but no files for transaction logging

yes

yes, write ahead logging

In-memory capabilities

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

depending on storage layer

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

yes, full featured in-memory storage engine with persistence

User concepts

Access control

yes

depending on the DBMS used for storage

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

yes

using Azure authentication

fine grained access rights according to SQL-standard

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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.