DBMS > Brytlyt vs. Geode vs. GeoMesa vs. Microsoft SQL Server

System Properties Comparison Brytlyt vs. Geode vs. GeoMesa vs. Microsoft SQL Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

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

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

Microsofts flagship relational DBMS

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.29
Rank	#288	Overall
	#131	Relational DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

brytlyt.io

geode.apache.org

www.geomesa.org

www.microsoft.com/en-us/sql-server

Technical documentation

docs.brytlyt.io

geode.apache.org/docs

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

learn.microsoft.com/en-US/sql/sql-server

Developer

Brytlyt

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

CCRi and others

Microsoft

Initial release

2016

2002

2014

1989

Current release

5.0, August 2023

1.1, February 2017

4.0.5, February 2024

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache License 2.0

commercial

restricted free version is 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

C, C++ and CUDA

Java

Scala

C++

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

the JDK (8 or later) is also required

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

yes

specific XML-type available, but no XML query functionality.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (OQL)

yes

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

user defined functions

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

tables can be distributed across several files (horizontal partitioning); sharding through federation

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication

depending on storage layer

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual 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

yes, on a single node

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

depending on storage layer

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Access rights per client and object definable

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

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.