DBMS > Drizzle vs. Infobright vs. OrientDB vs. Sadas Engine

System Properties Comparison Drizzle vs. Infobright vs. OrientDB vs. Sadas Engine

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

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

Multi-model DBMS (Document, Graph, Key/Value)

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Primary database model

Relational DBMS

Document store
Graph DBMS
Key-value store

Relational DBMS

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

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	3.19
Rank	#93	Overall
	#16	Document stores
	#7	Graph DBMS
	#14	Key-value stores

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Website

ignitetech.com/softwarelibrary/infobrightdb

orientdb.org

www.sadasengine.com

Technical documentation

www.orientdb.com/docs/last/index.html

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

Developer

Drizzle project, originally started by Brian Aker

Ignite Technologies Inc.; formerly InfoBright Inc.

OrientDB LTD; CallidusCloud; SAP

SADAS s.r.l.

Initial release

2008

2005

2010

2006

Current release

7.2.4, September 2012

3.2.29, March 2024

8.0

License

Commercial or Open Source

Open Source

GNU GPL

commercial

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

Open Source

Apache version 2

commercial

free trial version available

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

C++

Java

C++

Server operating systems

FreeBSD
Linux
OS X

Linux
Windows

All OS with a Java JDK (>= JDK 6)

AIX
Linux
Windows

Data scheme

yes

schema-free

Schema can be enforced for whole record ("schema-full") or for some fields only ("schema-hybrid")

yes

Typing

predefined data types such as float or date

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

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL-like query language, no joins

yes

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

Tinkerpop technology stack with Blueprints, Gremlin, Pipes
Java API
RESTful HTTP/JSON API

JDBC
ODBC
Proprietary protocol

Supported programming languages

C
C++
Java
PHP

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

.Net
C
C#
C++
Clojure
Java
JavaScript
JavaScript (Node.js)
PHP
Python
Ruby
Scala

.Net
C
C#
C++
Groovy
Java
PHP
Python

Server-side scripts

Stored procedures

Java, Javascript

Triggers

hooks for callbacks inside the server can be used.

Hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

could be achieved with distributed queries

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

relationship in graphs

yes

Transaction concepts

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

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

managed by 'Learn by Usage'

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

Access rights for users and roles; record level security configurable

Access rights for users, groups and roles 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

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

Graph DBMS increased their popularity by 500% within the last 2 years
3 March 2015, Paul Andlinger

Graph DBMSs are gaining in popularity faster than any other database category
21 January 2014, Matthias Gelbmann

show all

Recent citations in the news

The 12 Best Graph Databases to Consider for 2024
22 October 2023, Solutions Review

OrientDB: A Flexible and Scalable Multi-Model NoSQL DBMS
21 January 2022, Open Source For You

Comparing Graph Databases II. Part 2: ArangoDB, OrientDB, and… | by Sam Bell
20 September 2019, Towards Data Science

Mining Botnet Targeting Redis and OrientDB Servers Made Almost $1 Million
2 February 2018, BleepingComputer

ArangoDB raises $10 million for NoSQL database management
14 March 2019, VentureBeat

provided by Google News

Share this page