DBMS > Apache Phoenix vs. Milvus vs. MySQL vs. Percona Server for MongoDB vs. Tarantool

System Properties Comparison Apache Phoenix vs. Milvus vs. MySQL vs. Percona Server for MongoDB vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

A DBMS designed for efficient storage of vector data and vector similarity searches

Widely used open source RDBMS

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

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Relational DBMS

Vector DBMS

Relational DBMS

Key/Value like access via memcached API

Document store

Document store
Key-value store
Relational DBMS

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	2.31
Rank	#113	Overall
	#3	Vector DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

phoenix.apache.org

milvus.io

www.mysql.com

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

www.tarantool.io

Technical documentation

phoenix.apache.org

milvus.io/docs/overview.md

dev.mysql.com/doc

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

www.tarantool.io/en/doc

Developer

Apache Software Foundation

Oracle

since 2010, originally MySQL AB, then Sun

Percona

Initial release

2014

2019

1995

2015

2008

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

2.3.4, January 2024

8.4.0, April 2024

3.4.10-2.10, November 2017

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL Version 2

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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.

Zilliz Cloud – Cloud-native service for Milvus

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C++, Go

C and C++

C++

C and C++

Server operating systems

Linux
Unix
Windows

Linux
macOS

10.14 or later
Windows

with WSL 2 enabled

FreeBSD
Linux
OS X
Solaris
Windows

Linux

BSD
Linux
macOS

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

Vector, Numeric and String

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

Full-featured ANSI SQL support

APIs and other access methods

JDBC

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

proprietary protocol using JSON

Open binary protocol

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

C++
Go
Java
JavaScript (Node.js)
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

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

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

user defined functions

yes

proprietary syntax

JavaScript

Lua, C and SQL stored procedures

Triggers

yes

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Bounded Staleness
Eventual Consistency
Immediate Consistency
Session Consistency
Tunable Consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

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, full featured in-memory storage engine with persistence

User concepts

Access control

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

Role based access control and fine grained access rights

Users with fine-grained authorization concept

no user groups or roles

Access rights for users and roles

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

More information provided by the system vendor

Specific characteristics

Milvus is an open-source and cloud-native vector database built for production-ready...
» more

Competitive advantages

Highly available, versatile, and robust with millisecond latency. Supports batch...
» more

Typical application scenarios

RAG: retrieval augmented generation Video media : video understanding, video deduplication....
» more

Key customers

Milvus is trusted by thousands of enterprises, including PayPal, eBay, IKEA, LINE,...
» more

Market metrics

As of January 2024, 25k+ GitHub stars 10M+ downloads and installations 3k+ enterprise...
» more

Licensing and pricing models

Milvus was released under the open-source Apache License 2.0 in October 2019. Fully-managed...
» more

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.