DBMS > Axibase vs. Drizzle vs. Google Cloud Datastore vs. Netezza

System Properties Comparison Axibase vs. Drizzle vs. Google Cloud Datastore vs. Netezza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Scalable TimeSeries DBMS based on HBase with integrated rule engine and visualization

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

Data warehouse and analytics appliance part of IBM PureSystems

Primary database model

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

Score	0.32
Rank	#288	Overall
	#25	Time Series DBMS

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	10.18
Rank	#46	Overall
	#29	Relational DBMS

Website

axibase.com/docs/atsd/finance

cloud.google.com/datastore

www.ibm.com/products/netezza

Technical documentation

cloud.google.com/datastore/docs

Developer

Axibase Corporation

Drizzle project, originally started by Brian Aker

Google

IBM

Initial release

2013

2008

2000

Current release

15585

7.2.4, September 2012

License

Commercial or Open Source

commercial

Community Edition (single node) is free, Enterprise Edition (distributed) is paid

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

Java

C++

Server operating systems

Linux

FreeBSD
Linux
OS X

hosted

Linux

included in appliance

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

short, integer, long, float, double, decimal, string

yes

yes, details here

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

with proprietary extensions

SQL-like query language (GQL)

yes

APIs and other access methods

JDBC
Proprietary protocol (Network API)
RESTful HTTP API

JDBC

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

JDBC
ODBC
OLE DB

Supported programming languages

Go
Java
PHP
Python
R
Ruby

C
C++
Java
PHP

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C
C++
Fortran
Java
Lua
Perl
Python
R

Server-side scripts

Stored procedures

yes

using Google App Engine

yes

Triggers

yes

hooks for callbacks inside the server can be used.

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

Multi-source replication using Paxos

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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.

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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 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

Google Cloud is NOT magicking away data egress fees
12 January 2024, The Stack

SAP adds vector datastore to HANA Cloud database
2 November 2023, Techzine Europe

NetApp Cloud Volumes Service datastore support for Google Cloud VMware Engine
7 February 2023, NetApp

Your Memories. Their Cloud.
1 January 2023, The New York Times

All of Google’s cloud database services are now out of beta
16 August 2016, TechCrunch

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

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