DBMS > FatDB vs. Microsoft Access vs. SQLite vs. Weaviate

System Properties Comparison FatDB vs. Microsoft Access vs. SQLite vs. Weaviate

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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.)

Widely used embeddable, in-process RDBMS

An AI-native realtime vector database engine that integrates scalable machine learning models.

Primary database model

Document store
Key-value store

Relational DBMS

Vector DBMS

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

Score	104.92
Rank	#11	Overall
	#8	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	1.73
Rank	#143	Overall
	#5	Vector DBMS

Website

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

www.sqlite.org

github.com/weaviate/weaviate
weaviate.io

Technical documentation

developer.microsoft.com/en-us/access

www.sqlite.org/docs.html

weaviate.io/developers/weaviate

Developer

FatCloud

Microsoft

Dwayne Richard Hipp

Weaviate B.V.

Initial release

2012

1992

2000

2019

Current release

1902 (16.0.11328.20222), March 2019

3.45.3 (15 April 2024), April 2024

1.19, May 2023

License

Commercial or Open Source

commercial

Bundled with Microsoft Office

Open Source

Public Domain

Open Source

commercial license available with Weaviate 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.

Implementation language

C++

Server operating systems

Windows

Not a real database server, but making use of DLLs

server-less

Data scheme

schema-free

yes

dynamic column types

yes, maps to GraphQL interface

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

yes

string, int, float, geo point, date, cross reference, fuzzy references

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 data objects are indexed in a semantic vector space (the Contextionary), all primitive fields are indexed

SQL

Support of SQL

Via inetgration in SQL Server

yes

but not compliant to any SQL standard

yes

SQL-92 is not fully supported

GraphQL is used as query language

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

ADO.NET
DAO
ODBC
OLE DB

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

GraphQL query language
RESTful HTTP/JSON API

Supported programming languages

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

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

JavaScript / TypeScript
Python

Server-side scripts

Stored procedures

yes

via applications

yes

since Access 2010 using the ACE-engine

Triggers

yes

via applications

yes

since Access 2010 using the ACE-engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

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

Can implement custom security layer via applications

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

API Keys
OpenID Connect Discovery

More information provided by the system vendor

Specific characteristics

Weaviate is an open source vector database that is robust, scalable, cloud-native,...
» more

Competitive advantages

Flexible deployment - Free, open source or fully-managed cloud vector database service...
» more

Typical application scenarios

As a database supporting the development of generative AI and semantic search applications...
» more

Key customers

All companies that have data.
» more

Market metrics

As of mid 2023: Over 2 million open source downloads 3500+ Weaviate Slack community...
» more

Licensing and pricing models

Weaviate is open-source, and free to use. Weaviate is also available as a 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.