DBMS > Newts vs. PostGIS vs. Vitess vs. VoltDB

System Properties Comparison Newts vs. PostGIS vs. Vitess vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Time Series DBMS based on Cassandra

Spatial extension of PostgreSQL

Scalable, distributed, cloud-native DBMS, extending MySQL

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Time Series DBMS

Spatial DBMS

Relational DBMS

Secondary database models

Relational DBMS

Document store
Spatial DBMS

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

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

opennms.github.io/newts

postgis.net

vitess.io

www.voltdb.com

Technical documentation

github.com/OpenNMS/newts/wiki

postgis.net/documentation

vitess.io/docs

docs.voltdb.com

Developer

OpenNMS Group

The Linux Foundation, PlanetScale

VoltDB Inc.

Initial release

2014

2005

2013

2010

Current release

3.4.2, February 2024

15.0.2, December 2022

11.3, April 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL v2.0

Open Source

Apache Version 2.0, commercial licenses available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Server operating systems

Linux
OS X
Windows

Docker
Linux
macOS

Linux
OS X

for development

Data scheme

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

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

only a subset of SQL 99

APIs and other access methods

HTTP REST
Java API

ADO.NET
JDBC
MySQL protocol
ODBC

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

Java

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

yes

based on PostgreSQL

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

yes

based on PostgreSQL

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

ACID at shard level

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

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

yes

User concepts

Access control

yes

based on PostgreSQL

Users with fine-grained authorization concept

no user groups or roles

Users and roles with access to stored procedures

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

Farewell, Froggy: The Age of Ribbit Is Nearing an End
25 May 2013, Mother Jones

provided by Google News

Vitess, the database clustering system powering YouTube, graduates CNCF incubation
5 November 2019, SiliconANGLE News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page