DBMS > Firebase Realtime Database vs. LokiJS vs. Microsoft Access vs. Milvus vs. SQLite

System Properties Comparison Firebase Realtime Database vs. LokiJS vs. Microsoft Access vs. Milvus vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

In-memory JavaScript DBMS

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

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

Widely used embeddable, in-process RDBMS

Primary database model

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.43
Rank	#264	Overall
	#42	Document stores

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	2.31
Rank	#113	Overall
	#3	Vector DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

firebase.google.com/products/realtime-database

github.com/techfort/LokiJS

www.microsoft.com/en-us/microsoft-365/access

milvus.io

www.sqlite.org

Technical documentation

firebase.google.com/docs/database

techfort.github.io/LokiJS

developer.microsoft.com/en-us/access

milvus.io/docs/overview.md

www.sqlite.org/docs.html

Developer

Google

acquired by Google 2014

Microsoft

Dwayne Richard Hipp

Initial release

2012

2014

1992

2019

2000

Current release

1902 (16.0.11328.20222), March 2019

2.3.4, January 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

commercial

Bundled with Microsoft Office

Open Source

Apache Version 2.0

Open Source

Public Domain

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

JavaScript

C++

C++, Go

Server operating systems

hosted

server-less, requires a JavaScript environment (browser, Node.js)

Windows

Not a real database server, but making use of DLLs

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.

Secondary indexes

yes

via views

yes

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

SQL-92 is not fully supported

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

JavaScript API

ADO.NET
DAO
ODBC
OLE DB

RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Java
JavaScript
Objective-C

JavaScript

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

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

limited functionality with using 'rules'

View functions in JavaScript

yes

since Access 2010 using the ACE-engine

Triggers

Callbacks are triggered when data changes

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

none

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

yes

atomic operations within a single collection possible

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

yes

but no files for transaction logging

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

yes, based on authentication and database rules

a simple user-level security was built in till version Access 2003

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.