DBMS > 4D vs. Atos Standard Common Repository vs. Drizzle vs. Infobright vs. Netezza

System Properties Comparison 4D vs. Atos Standard Common Repository vs. Drizzle vs. Infobright vs. Netezza

Editorial information provided by DB-Engines

Name

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

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

Application development environment with integrated database management system

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

Data warehouse and analytics appliance part of IBM PureSystems

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	9.06
Rank	#46	Overall
	#29	Relational DBMS

Website

www.4d.com

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

ignitetech.com/softwarelibrary/infobrightdb

www.ibm.com/products/netezza

Technical documentation

developer.4d.com

Developer

4D, Inc

Atos Convergence Creators

Drizzle project, originally started by Brian Aker

Ignite Technologies Inc.; formerly InfoBright Inc.

IBM

Initial release

1984

2016

2008

2005

2000

Current release

v20, April 2023

1703

7.2.4, September 2012

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

commercial

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

OS X
Windows

Linux

FreeBSD
Linux
OS X

Linux
Windows

Linux

included in appliance

Data scheme

yes

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

yes

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

Secondary indexes

yes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

close to SQL 92

yes

with proprietary extensions

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

LDAP

JDBC

ADO.NET
JDBC
ODBC

JDBC
ODBC
OLE DB

Supported programming languages

4D proprietary IDE
PHP

All languages with LDAP bindings

C
C++
Java
PHP

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C++
Fortran
Java
Lua
Perl
Python
R

Server-side scripts

Stored procedures

yes

Triggers

yes

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

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

ACID

Atomic execution of specific operations

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

Users and groups

LDAP bind authentication

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Users with fine-grained authorization concept

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

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, 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.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

Netezza Performance Server
12 August 2020, ibm.com

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

provided by Google News

Share this page