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

System Properties Comparison Atos Standard Common Repository vs. Netezza vs. OrigoDB 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.

Description

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

Data warehouse and analytics appliance part of IBM PureSystems

A fully ACID in-memory object graph database

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

Document store
Object oriented DBMS

Relational DBMS

Spatial DBMS

Secondary database models

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.03
Rank	#378	Overall
	#51	Document stores
	#18	Object oriented 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

www.ibm.com/products/netezza

origodb.com

www.postgres-xl.org

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

Technical documentation

origodb.com/docs

www.postgres-xl.org/documentation

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

Developer

Atos Convergence Creators

IBM

Robert Friberg et al

Alessandro Furieri

Initial release

2016

2000

2009

under the name LiveDB

2014

since 2012, originally named StormDB

2008

Current release

1703

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

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C++

Server operating systems

Linux

included in appliance

Linux
Windows

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

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.

yes

can be achieved using .NET

yes

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

distributed, parallel query execution

yes

APIs and other access methods

LDAP

JDBC
ODBC
OLE DB

.NET Client API
HTTP API
LINQ

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

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

Server-side scripts

Stored procedures

yes

user defined functions

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

horizontal partitioning

client side managed; servers are not synchronized

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

depending on model

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

Write ahead log

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

Users with fine-grained authorization concept

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

Recent citations in the news

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

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