DBMS > Oracle NoSQL vs. PostGIS vs. RRDtool vs. SQLite

System Properties Comparison Oracle NoSQL vs. PostGIS vs. RRDtool vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Spatial extension of PostgreSQL

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Key-value store
Relational DBMS

Spatial DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	2.96
Rank	#103	Overall
	#18	Document stores
	#17	Key-value stores
	#52	Relational DBMS

Score	23.90
Rank	#29	Overall
	#1	Spatial DBMS

Score	2.14
Rank	#124	Overall
	#10	Time Series DBMS

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

www.oracle.com/database/nosql/technologies/nosql

postgis.net

oss.oetiker.ch/rrdtool

www.sqlite.org

Technical documentation

docs.oracle.com/en/database/other-databases/nosql-database/index.html

postgis.net/documentation

oss.oetiker.ch/rrdtool/doc

www.sqlite.org/docs.html

Developer

Oracle

Tobias Oetiker

Dwayne Richard Hipp

Initial release

2011

2005

1999

2000

Current release

23.3, December 2023

3.4.2, February 2024

1.8.0, 2022

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

GPL v2.0

Open Source

GPL V2 and FLOSS

Open Source

Public Domain

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

Java

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

Linux
Solaris SPARC/x86

HP-UX
Linux

server-less

Data scheme

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

dynamic column types

Typing

predefined data types such as float or date

optional

yes

Numeric data only

yes

not rigid because of 'dynamic typing' concept.

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

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

in-process shared library
Pipes

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
C#
Go
Java
JavaScript (Node.js)
Python

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

none

Replication methods

Methods for redundantly storing data on multiple nodes

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

yes

based on PostgreSQL

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

none

Foreign keys

Referential integrity

yes

Transaction concepts

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

configurable

ACID within a storage node (=shard)

ACID

Concurrency

Support for concurrent manipulation of data

yes

by using the rrdcached daemon

yes

via file-system locks

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.

yes

off heap cache

yes

User concepts

Access control

Access rights for users and roles

yes

based on PostgreSQL

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.