DBMS > Ehcache vs. Milvus vs. MySQL vs. PostGIS vs. Sequoiadb

System Properties Comparison Ehcache vs. Milvus vs. MySQL vs. PostGIS vs. Sequoiadb

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

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

Widely used open source RDBMS

Spatial extension of PostgreSQL

NewSQL database with distributed OLTP and SQL

Primary database model

Key-value store

Vector DBMS

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Document store
Relational DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	2.78
Rank	#103	Overall
	#3	Vector DBMS

Score	1061.34
Rank	#2	Overall
	#2	Relational DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Website

Technical documentation

www.ehcache.org/documentation

milvus.io/docs/overview.md

dev.mysql.com/doc

postgis.net/documentation

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

Terracotta Inc, owned by Software AG

Oracle

since 2010, originally MySQL AB, then Sun

Sequoiadb Ltd.

Initial release

2009

2019

1995

2005

2013

Current release

3.10.0, March 2022

2.3.4, January 2024

8.4.0, April 2024

3.4.2, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache Version 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL v2.0

Open Source

Server: AGPL; Client: Apache V2

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

Server operating systems

All OS with a Java VM

Linux
macOS

10.14 or later
Windows

with WSL 2 enabled

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

Vector, Numeric and String

yes

oid, date, timestamp, binary, regex

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

SQL-like query language

APIs and other access methods

JCache

RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

proprietary protocol using JSON

Supported programming languages

Java

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

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

JavaScript

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

based on PostgreSQL

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Bounded Staleness
Eventual Consistency
Immediate Consistency
Session Consistency
Tunable Consistency

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

not for MyISAM storage engine

ACID

Document is locked during a transaction

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

Role based access control and fine grained access rights

Users with fine-grained authorization concept

no user groups or roles

yes

based on PostgreSQL

simple password-based access control

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.