DBMS > GeoMesa vs. Microsoft Azure Synapse Analytics vs. Oracle Berkeley DB vs. WakandaDB

System Properties Comparison GeoMesa vs. Microsoft Azure Synapse Analytics vs. Oracle Berkeley DB vs. WakandaDB

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.

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

Widely used in-process key-value store

WakandaDB is embedded in a server that provides a REST API and a server-side javascript engine to access data

Primary database model

Spatial DBMS

Relational DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Object oriented DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	20.56
Rank	#31	Overall
	#19	Relational DBMS

Score	2.21
Rank	#117	Overall
	#20	Key-value stores
	#3	Native XML DBMS

Score	0.03
Rank	#364	Overall
	#17	Object oriented DBMS

Website

www.geomesa.org

azure.microsoft.com/services/synapse-analytics

www.oracle.com/database/technologies/related/berkeleydb.html

wakanda.github.io

Technical documentation

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

docs.microsoft.com/azure/synapse-analytics

docs.oracle.com/cd/E17076_05/html/index.html

wakanda.github.io/doc

Developer

CCRi and others

Microsoft

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Wakanda SAS

Initial release

2014

2016

1994

2012

Current release

4.0.5, February 2024

18.1.40, May 2020

2.7.0 (April 29, 2019), April 2019

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

commercial license available

Open Source

AGPLv3, extended commercial license available

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, Java, C++ (depending on the Berkeley DB edition)

C++, JavaScript

Server operating systems

hosted

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

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

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

APIs and other access methods

ADO.NET
JDBC
ODBC

RESTful HTTP API

Supported programming languages

C#
Java
PHP

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

JavaScript

Server-side scripts

Stored procedures

Transact SQL

yes

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

Source-replica replication

none

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

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

User concepts

Access control

yes

depending on the DBMS used for storage

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.

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

Recent citations in the news

Migrate Microsoft Azure Synapse Analytics to Amazon Redshift using AWS SCT | Amazon Web Services
18 October 2023, AWS Blog

Azure Synapse Runtime for Apache Spark 3.2 End of Support | Azure updates
22 March 2024, Microsoft

Azure Synapse vs. Databricks: Data Platform Comparison 2024
26 March 2024, eWeek

Azure Synapse Analytics: Everything you need to know about Microsoft's cloud analytics platform
24 September 2023, DataScientest

Azure Synapse Link for Cosmos DB: New Analytics Capabilities
10 November 2023, InfoQ.com

provided by Google News

ACM recognizes far-reaching technical achievements with special awards
26 May 2021, EurekAlert

EC will investigate the Oracle/Sun takeover due to concerns about MySQL
3 September 2009, The Guardian

Database Trends Report: SQL Beats NoSQL, MySQL Most Popular -- ADTmag
5 March 2019, ADT Magazine

A Quick Look at Open Source Databases for Mobile App Development
29 April 2018, Open Source For You

provided by Google News

Share this page