DBMS > Hazelcast vs. Ingres vs. Milvus vs. SQLite

System Properties Comparison Hazelcast vs. Ingres vs. Milvus vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted in-memory data grid

Well established RDBMS

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

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Document store

JSON support with IMDG 3.12

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

Score	6.87
Rank	#55	Overall
	#6	Key-value stores

Score	4.67
Rank	#77	Overall
	#42	Relational DBMS

Score	1.81
Rank	#144	Overall
	#5	Vector DBMS

Score	116.01
Rank	#10	Overall
	#7	Relational DBMS

Website

hazelcast.com

www.actian.com/databases/ingres

milvus.io

www.sqlite.org

Technical documentation

hazelcast.org/imdg/docs

docs.actian.com/ingres

milvus.io/docs/overview.md

www.sqlite.org/docs.html

Developer

Hazelcast

Actian Corporation

Dwayne Richard Hipp

Initial release

2008

1974

originally developed at University Berkely in early 1970s

2019

2000

Current release

5.3.6, November 2023

11.2, May 2022

2.3.4, January 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

Apache Version 2.0

Open Source

Public Domain

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

Implementation language

Java

C++, Go

Server operating systems

All OS with a Java VM

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux
macOS

10.14 or later
Windows

with WSL 2 enabled

server-less

Data scheme

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Vector, Numeric and String

yes

not rigid because of 'dynamic typing' concept.

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

the object must implement a serialization strategy

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

yes

SQL-92 is not fully supported

APIs and other access methods

JCache
JPA
Memcached protocol
RESTful HTTP API

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C#
C++
Clojure
Go
Java
JavaScript (Node.js)
Python
Scala

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

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Event Listeners, Executor Services

yes

Triggers

yes

Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Replicated Map

Ingres Replicator

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency selectable by user

Raft Consensus Algorithm

Immediate Consistency

Bounded Staleness
Eventual Consistency
Immediate Consistency
Session Consistency
Tunable Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

one or two-phase-commit; repeatable reads; read commited

ACID

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

via file-system locks

Durability

Support for making data persistent

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

fine grained access rights according to SQL-standard

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.