DBMS > GeoMesa vs. Oracle Berkeley DB vs. PouchDB vs. Valentina Server

System Properties Comparison GeoMesa vs. Oracle Berkeley DB vs. PouchDB vs. Valentina Server

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.

Widely used in-process key-value store

JavaScript DBMS with an API inspired by CouchDB

Object-relational database and reports server

Primary database model

Spatial DBMS

Key-value store

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Document store

Relational DBMS

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

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	1.88
Rank	#130	Overall
	#23	Key-value stores
	#3	Native XML DBMS

Score	2.18
Rank	#114	Overall
	#21	Document stores

Score	0.18
Rank	#313	Overall
	#140	Relational DBMS

Website

www.geomesa.org

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

pouchdb.com

www.valentina-db.net

Technical documentation

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

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

pouchdb.com/guides

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

CCRi and others

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Apache Software Foundation

Paradigma Software

Initial release

2014

1994

2012

1999

Current release

5.0.1, July 2024

18.1.40, May 2020

7.1.1, June 2019

5.7.5

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

commercial license available

Open Source

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Scala

C, Java, C++ (depending on the Berkeley DB edition)

JavaScript

Server operating systems

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

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

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

via views

yes

SQL

Support of SQL

yes

SQL interfaced based on SQLite is available

yes

APIs and other access methods

HTTP REST

only for PouchDB Server
JavaScript API

ODBC

Supported programming languages

.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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

View functions in JavaScript

yes

Triggers

yes

only for the SQL API

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

none

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

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

Eventual Consistency

Foreign keys

Referential integrity

yes

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

by using IndexedDB, WebSQL or LevelDB as backend

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

fine grained access rights according to SQL-standard

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

New kids on the block: database management systems implemented in JavaScript
1 December 2014, Matthias Gelbmann

show all

Recent citations in the news

What is NoSQL (Not Only SQL database)?
28 February 2022, TechTarget

Margo I. Seltzer
18 August 2020, Berkman Klein Center

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

A complete beginners guide to installing a Bitcoin Full Node on Linux (2018 Edition)
3 May 2018, hackernoon.com

How to store financial market data for backtesting
26 January 2019, Towards Data Science

provided by Google News

Create Offline Web Apps Using Service Workers & PouchDB
7 March 2017, SitePoint

Getting Started with PouchDB Client-Side JavaScript Database
7 September 2016, SitePoint

Building an Offline First App with PouchDB
10 March 2014, SitePoint

provided by Google News

A Look at Valentina
18 April 2014, SitePoint

MySQL GUI Tools for Windows and Ubuntu/Linux: Top 8 free or open source
7 December 2018, H2S Media

provided by Google News

Share this page