DBMS > Drizzle vs. Google BigQuery vs. OpenEdge vs. Percona Server for MongoDB vs. TinkerGraph

System Properties Comparison Drizzle vs. Google BigQuery vs. OpenEdge vs. Percona Server for MongoDB vs. TinkerGraph

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.

Large scale data warehouse service with append-only tables

Application development environment with integrated database management system

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

A lightweight, in-memory graph engine that serves as a reference implementation of the TinkerPop3 API

Primary database model

Relational DBMS

Document store

Graph DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	3.51
Rank	#86	Overall
	#46	Relational DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Score	0.08
Rank	#348	Overall
	#35	Graph DBMS

Website

cloud.google.com/bigquery

www.progress.com/openedge

www.percona.com/mongodb/software/percona-server-for-mongodb

tinkerpop.apache.org/docs/current/reference/#tinkergraph-gremlin

Technical documentation

cloud.google.com/bigquery/docs

documentation.progress.com/output/ua/OpenEdge_latest

docs.percona.com/percona-distribution-for-mongodb

Developer

Drizzle project, originally started by Brian Aker

Google

Progress Software Corporation

Percona

Initial release

2008

2010

1984

2015

2009

Current release

7.2.4, September 2012

OpenEdge 12.2, March 2020

3.4.10-2.10, November 2017

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

GPL Version 2

Open Source

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

Java

Server operating systems

FreeBSD
Linux
OS X

hosted

AIX
HP-UX
Linux
Solaris
Windows

Linux

Data scheme

yes

schema-free

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

close to SQL 92

APIs and other access methods

JDBC

RESTful HTTP/JSON API

JDBC
ODBC

proprietary protocol using JSON

TinkerPop 3

Supported programming languages

C
C++
Java
PHP

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Progress proprietary ABL (Advanced Business Language)

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Groovy
Java

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

JavaScript

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

since Version 11.4

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

none

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optional

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

via In-Memory Engine

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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

Google Cloud Identity & Access Management (IAM)

Users and groups

Access rights for users and roles

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.