DBMS > Drizzle vs. FatDB vs. GeoSpock vs. JaguarDB vs. Machbase Neo

System Properties Comparison Drizzle vs. FatDB vs. GeoSpock vs. JaguarDB vs. Machbase Neo

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

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

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

Spatial and temporal data processing engine for extreme data scale

Performant, highly scalable DBMS for AI and IoT applications

TimeSeries DBMS for AIoT and BigData

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Key-value store
Vector DBMS

Time Series DBMS

Secondary database models

Time Series DBMS

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Website

geospock.com

www.jaguardb.com

machbase.com

Technical documentation

www.jaguardb.com/support.html

machbase.com/dbms

Developer

Drizzle project, originally started by Brian Aker

FatCloud

GeoSpock

DataJaguar, Inc.

Machbase

Initial release

2008

2012

2015

2013

Current release

7.2.4, September 2012

2.0, September 2019

3.3 July 2023

V8.0, August 2023

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

GPL V3.0

commercial

free test version available

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, Javascript

C++

the server part. Clients available in other languages

Server operating systems

FreeBSD
Linux
OS X

Windows

hosted

Linux

Linux
macOS
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

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

temporal, categorical

yes

SQL

Support of SQL

yes

with proprietary extensions

Via inetgration in SQL Server

ANSI SQL for query only (using Presto)

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language

APIs and other access methods

JDBC

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

JDBC

JDBC
ODBC

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

Supported programming languages

C
C++
Java
PHP

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

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

Server-side scripts

Stored procedures

yes

via applications

Triggers

hooks for callbacks inside the server can be used.

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic sharding

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

Multi-source replication

selectable replication factor

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

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

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.

yes

volatile and lookup table

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Can implement custom security layer via applications

Access rights for users can be defined per table

rights management via user accounts

simple password-based access control

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

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

How GeoSpock is supercharging geospatial analytics
23 February 2021, ComputerWeekly.com

GeoSpock launches Spatial Big Data Platform 2.0
4 September 2019, VanillaPlus

Cambridge-based data analytics startup GeoSpock lands €4.6 million
2 October 2020, EU-Startups

nChain Leads Investment Round in Extreme-scale Data Firm GeoSpock
2 October 2020, AlexaBlockchain

Smart Cities, Autonomous Vehicles, Artificial General Intelligence Robotics: Q&A with Steve Marsh, GeoSpock
16 May 2018, ExchangeWire

provided by Google News

Share this page