DBMS > 4D vs. Altibase vs. Atos Standard Common Repository vs. Drizzle vs. Snowflake

System Properties Comparison 4D vs. Altibase vs. Atos Standard Common Repository vs. Drizzle vs. Snowflake

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

An enterprise grade, high-performance RDBMS

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.

Cloud-based data warehousing service for structured and semi-structured data

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.68
Rank	#110	Overall
	#54	Relational DBMS

Score	1.00
Rank	#194	Overall
	#91	Relational DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

www.4d.com

altibase.com

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

www.snowflake.com

Technical documentation

developer.4d.com

github.com/ALTIBASE/Documents/tree/master/Manuals

docs.snowflake.net/manuals/index.html

Developer

4D, Inc

Altibase

Atos Convergence Creators

Drizzle project, originally started by Brian Aker

Snowflake Computing Inc.

Initial release

1984

1999

2016

2008

2014

Current release

v20, April 2023

v7.3, 2023, August 2023

1703

7.2.4, September 2012

License

Commercial or Open Source

commercial

Open source edition discontinued with March 2023

commercial

Open Source

GNU GPL

commercial

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

C++

Java

C++

Server operating systems

OS X
Windows

AIX
HP-UX
Linux

Linux

FreeBSD
Linux
OS X

hosted

Data scheme

yes

Schema and schema-less with LDAP views

yes

support of semi-structured data formats (JSON, XML, Avro)

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

SQL

Support of SQL

yes

close to SQL 92

ANSI SQL-92

yes

with proprietary extensions

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

JDBC
ODBC
Proprietary protocol

LDAP

JDBC

CLI Client
JDBC
ODBC

Supported programming languages

4D proprietary IDE
PHP

C
C++
Java

All languages with LDAP bindings

C
C++
Java
PHP

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

stored procedures and stored functions

user defined functions

Triggers

yes

hooks for callbacks inside the server can be used.

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

cell division

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

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

fine grained access rights according to SQL-standard

LDAP bind authentication

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Users with fine-grained authorization concept, user roles and pluggable authentication

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.