DBMS > Drizzle vs. Faircom EDGE vs. Google BigQuery vs. VictoriaMetrics

System Properties Comparison Drizzle vs. Faircom EDGE vs. Google BigQuery vs. VictoriaMetrics

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

Large scale data warehouse service with append-only tables

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Time Series 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	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

www.faircom.com/products/faircom-edge

cloud.google.com/bigquery

victoriametrics.com

Technical documentation

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

cloud.google.com/bigquery/docs

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Drizzle project, originally started by Brian Aker

FairCom Corporation

Google

VictoriaMetrics

Initial release

2008

1979

2010

2018

Current release

7.2.4, September 2012

V3, October 2020

v1.91, May 2023

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Restricted, free version available

commercial

Open Source

Apache Version 2.0

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

ANSI C, C++

Server operating systems

FreeBSD
Linux
OS X

Android
Linux

ARM, x86
Raspbian
Windows

hosted

FreeBSD
Linux
macOS
OpenBSD

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

yes

APIs and other access methods

JDBC

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

RESTful HTTP/JSON API

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

C
C++
Java
PHP

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

user defined functions

in JavaScript

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

File partitioning

Customizable business rules for partitioning

none

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

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency
Tunable Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

when using SQL

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

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.

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.