DBMS > FatDB vs. Geode vs. NSDb vs. OrigoDB vs. VictoriaMetrics

System Properties Comparison FatDB vs. Geode vs. NSDb vs. OrigoDB vs. VictoriaMetrics

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.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

A fully ACID in-memory object graph database

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Document store
Key-value store

Key-value store

Time Series DBMS

Document store
Object oriented DBMS

Time Series DBMS

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

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

Technical documentation

geode.apache.org/docs

nsdb.io/Architecture

origodb.com/docs

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

FatCloud

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Robert Friberg et al

VictoriaMetrics

Initial release

2012

2002

2017

2009

under the name LiveDB

2018

Current release

1.1, February 2017

v1.91, May 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0

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

Java, Scala

Server operating systems

Windows

All OS with a Java VM

the JDK (8 or later) is also required

Linux
macOS

Linux
Windows

FreeBSD
Linux
macOS
OpenBSD

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

User defined using .NET types and collections

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.

can be achieved using .NET

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

Via inetgration in SQL Server

SQL-like query language (OQL)

SQL-like query language

APIs and other access methods

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

Java Client API
Memcached protocol
RESTful HTTP API

gRPC
HTTP REST
WebSocket

.NET Client API
HTTP API
LINQ

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

.Net
All JVM based languages
C++
Groovy
Java
Scala

Java
Scala

.Net

Server-side scripts

Stored procedures

yes

via applications

user defined functions

yes

Triggers

yes

via applications

yes

Cache Event Listeners

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication

Source-replica replication

Synchronous replication

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

depending on model

Transaction concepts

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

yes, on a single node

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

yes

Write ahead log

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

Access rights per client and object definable

Role based authorization

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

Recent citations in the news

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

Victor I. Cazares Wants NYTW to Call for Ceasefire in Gaza
22 February 2024, Vulture

Reactive Event Processing with Apache Geode
5 July 2020, InfoQ.com

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, oreilly.com

Where Does Apache Geode Fit in CQRS Architectures?
18 December 2016, InfoQ.com

provided by Google News

Green coding - VictoriaMetrics: The efficiency vs complexity trade-off
15 May 2024, ComputerWeekly.com

KubeCon24: VictoriaMetrics' Simpler Alternative to Prometheus
20 March 2024, The New Stack

OpenTelemetry Is Too Complicated, VictoriaMetrics Says
1 April 2024, Datanami

How VictoriaMetrics' open source approach led to mass industry adoption
3 May 2024, Tech.eu

VictoriaMetrics takes organic growth over investor pressure
11 December 2023, The Register

provided by Google News

Share this page