DBMS > AgensGraph vs. Microsoft Access vs. SiriDB vs. Snowflake vs. Solr

System Properties Comparison AgensGraph vs. Microsoft Access vs. SiriDB vs. Snowflake vs. Solr

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

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

Open Source Time Series DBMS

Cloud-based data warehousing service for structured and semi-structured data

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Graph DBMS
Relational DBMS

Secondary database models

Spatial DBMS

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

Score	0.16
Rank	#333	Overall
	#30	Graph DBMS
	#146	Relational DBMS

Score	105.40
Rank	#11	Overall
	#8	Relational DBMS

Score	0.11
Rank	#346	Overall
	#32	Time Series DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Score	44.28
Rank	#24	Overall
	#3	Search engines

Website

bitnine.net/agensgraph

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

siridb.com

www.snowflake.com

solr.apache.org

Technical documentation

bitnine.net/documentation

developer.microsoft.com/en-us/access

docs.siridb.com

docs.snowflake.net/manuals/index.html

solr.apache.org/resources.html

Developer

Bitnine Global Inc.

Microsoft

Cesbit

Snowflake Computing Inc.

Apache Software Foundation

Initial release

2016

1992

2017

2014

2006

Current release

2.1, December 2018

1902 (16.0.11328.20222), March 2019

9.5.0, February 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Bundled with Microsoft Office

Open Source

MIT License

commercial

Open Source

Apache Version 2

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.

Implementation language

C++

Java

Server operating systems

Linux
OS X
Windows

Windows

Not a real database server, but making use of DLLs

Linux

hosted

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

depending on used data model

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

Numeric data

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

SQL

Support of SQL

yes

but not compliant to any SQL standard

yes

Solr Parallel SQL Interface

APIs and other access methods

Cypher Query Language
JDBC

ADO.NET
DAO
ODBC
OLE DB

HTTP API

CLI Client
JDBC
ODBC

Java API
RESTful HTTP/JSON API

Supported programming languages

C
Java
JavaScript
Python

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

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

JavaScript (Node.js)
Python

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

yes

since Access 2010 using the ACE-engine

user defined functions

Java plugins

Triggers

yes

since Access 2010 using the ACE-engine

similar concept for controling cloud resources

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

none

Sharding

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

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

optimistic locking

Concurrency

Support for concurrent manipulation of data

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

fine grained access rights according to SQL-standard

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

simple rights management via user accounts

Users with fine-grained authorization concept, user roles and pluggable authentication

yes

More information provided by the system vendor

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.