DBMS > GeoMesa vs. OrigoDB vs. PouchDB vs. TimescaleDB

System Properties Comparison GeoMesa vs. OrigoDB vs. PouchDB vs. TimescaleDB

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.

A fully ACID in-memory object graph database

JavaScript DBMS with an API inspired by CouchDB

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Spatial DBMS

Document store
Object oriented DBMS

Document store

Time Series DBMS

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	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

Technical documentation

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

origodb.com/docs

pouchdb.com/guides

docs.timescale.com

Developer

CCRi and others

Robert Friberg et al

Apache Software Foundation

Timescale

Initial release

2014

2009

under the name LiveDB

2012

2017

Current release

4.0.5, February 2024

7.1.1, June 2019

2.13.0, November 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

Open Source

Apache 2.0

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

JavaScript

Server operating systems

Linux
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

User defined using .NET types and collections

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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.

can be achieved using .NET

yes

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

full PostgreSQL SQL syntax

APIs and other access methods

.NET Client API
HTTP API
LINQ

HTTP REST

only for PouchDB Server
JavaScript API

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

.Net

JavaScript

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

View functions in JavaScript

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

horizontal partitioning

client side managed; servers are not synchronized

Sharding

with a proxy-based framework, named couchdb-lounge

yes, across time and space (hash partitioning) attributes

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

Source-replica replication with hot standby and reads on replicas

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

Immediate Consistency

Foreign keys

Referential integrity

depending on model

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

Write ahead log

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

Role based authorization

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

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

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

3 Reasons To Think Offline First
22 March 2017, IBM

Offline-first web and mobile apps: Top frameworks and components
22 January 2019, TechBeacon

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

provided by Google News

TimescaleDB Is a Vector Database Now, Too
25 September 2023, Datanami

Timescale Acquires PopSQL to Bring a Modern, Collaborative SQL GUI to PostgreSQL Developers
4 April 2024, PR Newswire

TimescaleDB for Azure Database for PostgreSQL to power IoT and time-series workloads | Azure updates
18 March 2019, azure.microsoft.com

Visualizing IoT Data at Scale With Hopara and TimescaleDB
16 May 2023, Embedded Computing Design

Timescale Valuation Rockets to Over $1B with $110M Round, Marking the Explosive Rise of Time-Series Data
22 February 2022, Business Wire

provided by Google News

Share this page