DBMS > FatDB vs. GeoMesa vs. Linter vs. SingleStore

System Properties Comparison FatDB vs. GeoMesa vs. Linter vs. SingleStore

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.

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

RDBMS for high security requirements

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

Primary database model

Document store
Key-value store

Spatial DBMS

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

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

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	0.03
Rank	#368	Overall
	#156	Relational DBMS

Score	4.02
Rank	#74	Overall
	#39	Relational DBMS

Website

www.geomesa.org

linter.ru

www.singlestore.com

Technical documentation

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

docs.singlestore.com

Developer

FatCloud

CCRi and others

relex.ru

SingleStore Inc.

Initial release

2012

2014

1990

2013

Current release

5.0.1, July 2024

8.5, January 2024

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

free developer edition available

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

Scala

C and C++

C++, Go

Server operating systems

Windows

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux

64 bit version required

Data scheme

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

SQL

Support of SQL

Via inetgration in SQL Server

yes

but no triggers and foreign keys

APIs and other access methods

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

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

Supported programming languages

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

Bash
C
C#
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

via applications

yes

proprietary syntax with the possibility to convert from PL/SQL

yes

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

none

Sharding

hash partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

depending on storage layer

Source-replica replication

stores two copies of each physical data partition on two separate nodes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

depending on storage layer

Immediate 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

yes, multi-version concurrency control (MVCC)

Durability

Support for making data persistent

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

yes

User concepts

Access control

Can implement custom security layer via applications

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

Fine grained access control via users, groups 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

Turbocharge Your Application Development Using WebAssembly With SingleStoreDB
17 October 2022, Akmal Chaudhri, SingleStore (sponsor)

Cloud-Based Analytics With SingleStoreDB
9 June 2022, Akmal Chaudhri, SingleStore (sponsor)

SingleStore: The Increasing Momentum of Multi-Model Database Systems
14 February 2022, Akmal Chaudhri, SingleStore (sponsor)

show all

Recent citations in the news

SingleStore Partners With Snowflake to Help Users Build Faster, More Efficient Real Time AI Applications
19 September 2024, businesswire.com

SingleStore CEO sees little future for purpose-built vector databases
24 January 2024, VentureBeat

Achieve near real-time analytics on Amazon DynamoDB with SingleStore
16 September 2024, AWS Blog

Building a Modern Database: Nikita Shamgunov on Postgres and Beyond
18 April 2024, Madrona Venture Group

SingleStore: We do vectors and you don’t need knowledge graphs
22 July 2024, Blocks & Files

provided by Google News

Share this page