DBMS > NSDb vs. OrigoDB vs. SpatiaLite vs. Tkrzw

System Properties Comparison NSDb vs. OrigoDB vs. SpatiaLite vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

A fully ACID in-memory object graph database

Spatial extension of SQLite

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Time Series DBMS

Document store
Object oriented DBMS

Spatial DBMS

Key-value store

Secondary database models

Relational DBMS

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

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

nsdb.io

origodb.com

www.gaia-gis.it/fossil/libspatialite/index

dbmx.net/tkrzw

Technical documentation

nsdb.io/Architecture

origodb.com/docs

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Robert Friberg et al

Alessandro Furieri

Mikio Hirabayashi

Initial release

2017

2009

under the name LiveDB

2008

2020

Current release

5.0.0, August 2020

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

Open Source

Apache Version 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

Java, Scala

C++

Server operating systems

Linux
macOS

Linux
Windows

server-less

Linux
macOS

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes: int, bigint, decimal, string

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

gRPC
HTTP REST
WebSocket

.NET Client API
HTTP API
LINQ

Supported programming languages

Java
Scala

.Net

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

Using Apache Lucene

yes

Write ahead log

yes

In-memory capabilities

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

yes

using specific database classes

User concepts

Access control

Role based authorization

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.