DBMS > Atos Standard Common Repository vs. GeoSpock vs. Netezza vs. Postgres-XL vs. SpatiaLite

System Properties Comparison Atos Standard Common Repository vs. GeoSpock vs. Netezza vs. Postgres-XL vs. SpatiaLite

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

Spatial and temporal data processing engine for extreme data scale

Data warehouse and analytics appliance part of IBM PureSystems

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

Spatial extension of SQLite

Primary database model

Document store
Key-value store

Relational DBMS

Spatial DBMS

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

Relational DBMS

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

Score	10.18
Rank	#46	Overall
	#29	Relational DBMS

Score	0.52
Rank	#256	Overall
	#117	Relational DBMS

Score	1.72
Rank	#149	Overall
	#3	Spatial DBMS

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

geospock.com

www.ibm.com/products/netezza

www.postgres-xl.org

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

Technical documentation

www.postgres-xl.org/documentation

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

Developer

Atos Convergence Creators

GeoSpock

IBM

Alessandro Furieri

Initial release

2016

2000

2014

since 2012, originally named StormDB

2008

Current release

1703

2.0, September 2019

10 R1, October 2018

5.0.0, August 2020

License

Commercial or Open Source

commercial

Open Source

Mozilla public license

Open Source

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

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Java, Javascript

C++

Server operating systems

Linux

hosted

Linux

included in appliance

Linux
macOS

server-less

Data scheme

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

optional

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

XML type, but no XML query functionality

Secondary indexes

yes

temporal, categorical

yes

SQL

Support of SQL

ANSI SQL for query only (using Presto)

yes

distributed, parallel query execution

yes

APIs and other access methods

LDAP

JDBC

JDBC
ODBC
OLE DB

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

Supported programming languages

All languages with LDAP bindings

C
C++
Fortran
Java
Lua
Perl
Python
R

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Automatic sharding

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

MVCC

ACID

Concurrency

Support for concurrent manipulation of data

yes

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

User concepts

Access control

LDAP bind authentication

Access rights for users can be defined per table

Users with fine-grained authorization concept

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

Recent citations in the news

How GeoSpock is supercharging geospatial analytics
23 February 2021, ComputerWeekly.com

Imagining an 'Everything Connected' World With Geospock | AWS Startups Blog
20 June 2019, AWS Blog

GeoSpock launches Spatial Big Data Platform 2.0
4 September 2019, VanillaPlus

nChain Leads Investment Round in Extreme-scale Data Firm GeoSpock
2 October 2020, AlexaBlockchain

GeoSpock receives $5.4m as strategic investment
5 October 2020, Geospatial World

provided by Google News

IBM announces availability of the high-performance, cloud-native Netezza Performance Server as a Service on AWS
11 July 2023, ibm.com

AWS and IBM Netezza come out in support of Iceberg in table format face-off
1 August 2023, The Register

Migrating your Netezza data warehouse to Amazon Redshift | Amazon Web Services
27 May 2020, AWS Blog

U.S. Navy Chooses Yellowbrick, Sunsets IBM Netezza
22 March 2023, Business Wire

IBM Brings Back a Netezza, Attacks Yellowbrick
29 June 2020, Datanami

provided by Google News

Share this page