DBMS > Drizzle vs. FatDB vs. Infobright vs. SpatiaLite

System Properties Comparison Drizzle vs. FatDB vs. Infobright vs. SpatiaLite

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.

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

Spatial extension of SQLite

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	0.96
Rank	#194	Overall
	#91	Relational DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Website

ignitetech.com/softwarelibrary/infobrightdb

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

Technical documentation

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

Developer

Drizzle project, originally started by Brian Aker

FatCloud

Ignite Technologies Inc.; formerly InfoBright Inc.

Alessandro Furieri

Initial release

2008

2012

2005

2008

Current release

7.2.4, September 2012

5.0.0, August 2020

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

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

C++

Server operating systems

FreeBSD
Linux
OS X

Windows

Linux
Windows

server-less

Data scheme

yes

schema-free

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

Via inetgration in SQL Server

yes

APIs and other access methods

JDBC

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

ADO.NET
JDBC
ODBC

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

Server-side scripts

Stored procedures

yes

via applications

Triggers

hooks for callbacks inside the server can be used.

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

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

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

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

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Can implement custom security layer via applications

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Ignite Buys Database Vendor Infobright
2 May 2017, Datanami

provided by Google News

Share this page