DBMS > Blazegraph vs. FatDB vs. GeoMesa vs. Percona Server for MongoDB

System Properties Comparison Blazegraph vs. FatDB vs. GeoMesa vs. Percona Server for MongoDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Amazon has acquired Blazegraph's domain and (probably) product. It is said that Amazon Neptune is based on Blazegraph.

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

Description

High-performance graph database supporting Semantic Web (RDF/SPARQL) and Graph Database (tinkerpop3, blueprints, vertex-centric) APIs with scale-out and High Availability.

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

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

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

Graph DBMS
RDF store

Document store
Key-value store

Spatial DBMS

Document store

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

Score	0.74
Rank	#217	Overall
	#19	Graph DBMS
	#8	RDF stores

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.50
Rank	#250	Overall
	#39	Document stores

Website

blazegraph.com

www.geomesa.org

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

wiki.blazegraph.com

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

docs.percona.com/percona-distribution-for-mongodb

Developer

Blazegraph

FatCloud

CCRi and others

Percona

Initial release

2006

2012

2014

2015

Current release

2.1.5, March 2019

5.0.1, July 2024

3.4.10-2.10, November 2017

License

Commercial or Open Source

Open Source

extended commercial license available

commercial

Open Source

Apache License 2.0

Open Source

GPL Version 2

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

Java

Scala

C++

Server operating systems

Linux
OS X
Windows

Windows

Linux

Data scheme

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

RDF literal types

yes

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

SQL

Support of SQL

SPARQL is used as query language

Via inetgration in SQL Server

APIs and other access methods

Java API
RESTful HTTP API
SPARQL QUERY
SPARQL UPDATE
TinkerPop 3

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

proprietary protocol using JSON

Supported programming languages

.Net
C
C++
Java
JavaScript
PHP
Python
Ruby

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

yes

via applications

JavaScript

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

depending on storage layer

Source-replica replication

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 depending on configuration

Eventual Consistency
Immediate Consistency

depending on storage layer

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Relationships in Graphs

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

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.

depending on storage layer

yes

via In-Memory Engine

User concepts

Access control

Security and Authentication via Web Application Container (Tomcat, Jetty)

Can implement custom security layer via applications

yes

depending on the DBMS used for storage

Access rights for users and roles

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Video: Blazegraph Accelerates Graph Computing with GPUs
20 December 2015, insideHPC

Harnessing GPUs Delivers a Big Speedup for Graph Analytics
15 December 2015, Datanami

This AI Paper Introduces A Comprehensive RDF Dataset With Over 26 Billion Triples Covering Scholarly Data Across All Scientific Disciplines
19 August 2023, MarkTechPost

provided by Google News

Percona launches management system aimed at open-source databases
17 May 2022, The Register

Is database-as-a-service in Percona’s future?
23 May 2022, VentureBeat

FerretDB goes GA: Gives you MongoDB, without the MongoDB...
15 May 2023, The Stack

The essential guide to MongoDB security
2 February 2017, InfoWorld

Supercharge your Amazon RDS for MySQL deployment with ProxySQL and Percona Monitoring and Management
12 October 2018, AWS Blog

provided by Google News

Share this page