DBMS > Drizzle vs. Faircom EDGE vs. Ignite

System Properties Comparison Drizzle vs. Faircom EDGE vs. Ignite

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.

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

Primary database model

Relational DBMS

Key-value store
Relational DBMS

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

Score	0.02
Rank	#368	Overall
	#54	Key-value stores
	#156	Relational DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Website

www.faircom.com/products/faircom-edge

ignite.apache.org

Technical documentation

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

apacheignite.readme.io/docs

Developer

Drizzle project, originally started by Brian Aker

FairCom Corporation

Apache Software Foundation

Initial release

2008

1979

2015

Current release

7.2.4, September 2012

V3, October 2020

Apache Ignite 2.6

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Restricted, free version available

Open Source

Apache 2.0

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

ANSI C, C++

C++, Java, .Net

Server operating systems

FreeBSD
Linux
OS X

Android
Linux

ARM, x86
Raspbian
Windows

Linux
OS X
Solaris
Windows

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

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

with proprietary extensions

yes

ANSI SQL queries

ANSI-99 for query and DML statements, subset of DDL

APIs and other access methods

JDBC

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

Supported programming languages

C
C++
Java
PHP

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

C#
C++
Java
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes (compute grid and cache interceptors can be used instead)

Triggers

hooks for callbacks inside the server can be used.

yes

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

File partitioning

Customizable business rules for partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

Synchronous and asynchronous realtime replication based on transaction logs

yes (replicated cache)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency
Tunable Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

when using SQL

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

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

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

Security Hooks for custom implementations

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

Innovative Software and Giant Lego Sets, Why FairCom Edge Booth is a Must-Visit at Automate
9 May 2024, MVPro

FairCom kicks off new era of database technology USA - English
10 November 2020, PR Newswire

Brokers, Protocols, Platform Move Manufacturing Data
26 July 2023, EE Times

Winners of the 2021 IoT Evolution Product of the Year Awards Announced
6 July 2021, IoT Evolution World

Trend-Setting Products in Data and Information Management for 2023
8 December 2022, Database Trends and Applications

provided by Google News

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

Apache Ignite: An Overview
6 September 2023, Open Source For You

GridGain Releases Conference Schedule for Virtual Apache Ignite Summit 2023
1 June 2023, Datanami

What is Apache Ignite? How is Apache Ignite Used?
18 July 2022, The Stack

Real-time in-memory OLTP and Analytics with Apache Ignite on AWS | Amazon Web Services
14 May 2016, AWS Blog

provided by Google News

Share this page