DBMS > BigObject vs. Drizzle vs. Ehcache vs. Percona Server for MongoDB

System Properties Comparison BigObject vs. Drizzle vs. Ehcache vs. Percona Server for MongoDB

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

Analytic DBMS for real-time computations and queries

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

A widely adopted Java cache with tiered storage options

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

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Key-value store

Document store

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	0.52
Rank	#254	Overall
	#39	Document stores

Website

bigobject.io

www.ehcache.org

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

Technical documentation

docs.bigobject.io

www.ehcache.org/documentation

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

Developer

BigObject, Inc.

Drizzle project, originally started by Brian Aker

Terracotta Inc, owned by Software AG

Percona

Initial release

2015

2008

2009

2015

Current release

7.2.4, September 2012

3.10.0, March 2022

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

free community edition available

Open Source

GNU GPL

Open Source

Apache Version 2; commercial licenses available

Open Source

GPL Version 2

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

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

FreeBSD
Linux
OS X

All OS with a Java VM

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

with proprietary extensions

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

JDBC

JCache

proprietary protocol using JSON

Supported programming languages

C
C++
Java
PHP

Java

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

Server-side scripts

Stored procedures

Lua

JavaScript

Triggers

hooks for callbacks inside the server can be used.

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

by using Terracotta Server

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes

by using Terracotta Server

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

ACID

yes

supports JTA and can work as an XA resource

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

In-memory capabilities

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

yes

via In-Memory Engine

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.

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

Jira Data Center user? Here's a critical Ehcache vulnerability to spoil your day
22 July 2021, The Register

Atlassian asks customers to patch critical Jira vulnerability
22 July 2021, BleepingComputer

Critical Jira Flaw in Atlassian Could Lead to RCE
22 July 2021, Threatpost

Migration From JBoss 5 to JBoss 7: All It Takes Is 11 Easy Steps
3 June 2021, hackernoon.com

DZone Coding Java JBoss 5 to 7 in 11 steps
9 January 2014, dzone.com

provided by Google News

5 Reasons to Run MongoDB on Kubernetes
6 March 2024, The New Stack

A New Way to Provision Databases on Kubernetes
21 March 2024, hackernoon.com

FerretDB goes GA: Gives you MongoDB, without the MongoDB...
15 May 2023, The Stack

Unlock MongoDB's Full Potential: Ensuring Post-Upgrade Success
22 February 2024, The New Stack

Percona launches management system aimed at open-source databases
17 May 2022, The Register

provided by Google News

Share this page