DBMS > GeoMesa vs. HarperDB vs. Microsoft Azure Cosmos DB vs. Milvus

System Properties Comparison GeoMesa vs. HarperDB vs. Microsoft Azure Cosmos DB vs. Milvus

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

HarperDB takes the "stack" out of "tech stack" by combining an ultra-fast document-style data store, in-memory cache, real-time message broker, and your application components into a single distributed technology.

Globally distributed, horizontally scalable, multi-model database service

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

Primary database model

Spatial DBMS

Document store

Document store
Graph DBMS
Key-value store
Wide column store

Vector DBMS

Secondary database models

Spatial DBMS

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

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.55
Rank	#243	Overall
	#38	Document stores

Score	24.97
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	3.01
Rank	#89	Overall
	#4	Vector DBMS

Website

www.geomesa.org

www.harperdb.io

azure.microsoft.com/services/cosmos-db

milvus.io

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

docs.harperdb.io/docs

learn.microsoft.com/azure/cosmos-db

milvus.io/docs/overview.md

Developer

CCRi and others

HarperDB

Microsoft

Initial release

2014

2017

2014

2019

Current release

5.0.1, July 2024

3.1, August 2021

2.4.4, May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free community edition 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.

Zilliz Cloud – Cloud-native service for Milvus

Implementation language

Scala

Node.js

C++, Go

Server operating systems

Linux
OS X

hosted

Linux
macOS

10.14 or later
Windows

with WSL 2 enabled

Data scheme

yes

dynamic schema

schema-free

Typing

predefined data types such as float or date

yes

JSON data types

yes

JSON types

Vector, Numeric and String

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

All properties auto-indexed by default

SQL

Support of SQL

SQL-like data manipulation statements

SQL-like query language

APIs and other access methods

JDBC
ODBC
React Hooks
RESTful HTTP/JSON API
WebSocket

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

RESTful HTTP API

Supported programming languages

.Net
C
C#
C++
ColdFusion
D
Dart
Delphi
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Lisp
MatLab
Objective C
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Rust
Scala
Swift

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

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

Server-side scripts

Stored procedures

Custom Functions

since release 3.1

JavaScript

Triggers

JavaScript

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

A table resides as a whole on one (or more) nodes in a cluster

Sharding

Implicit feature of the cloud service

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

yes

the nodes on which a table resides can be defined

yes

Implicit feature of the cloud service

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Bounded Staleness
Eventual Consistency
Immediate Consistency
Session Consistency
Tunable Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

Multi-item ACID transactions with snapshot isolation within a partition

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, using LMDB

yes

In-memory capabilities

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

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Access rights for users and roles

Access rights can be defined down to the item level

Role based access control and fine grained access rights

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.