DBMS > Brytlyt vs. GeoMesa vs. Greenplum vs. Microsoft SQL Server vs. Qdrant

System Properties Comparison Brytlyt vs. GeoMesa vs. Greenplum vs. Microsoft SQL Server vs. Qdrant

Editorial information provided by DB-Engines

Name

Description

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

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

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

Microsofts flagship relational DBMS

A high-performance vector database with neural network or semantic-based matching

Primary database model

Secondary database models

Document store
Spatial DBMS

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	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Website

brytlyt.io

www.geomesa.org

greenplum.org

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

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

docs.brytlyt.io

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

docs.greenplum.org

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

qdrant.tech/documentation

Developer

Brytlyt

CCRi and others

Pivotal Software Inc.

Microsoft

Qdrant

Initial release

2016

2014

2005

1989

2021

Current release

5.0, August 2023

4.0.5, February 2024

7.0.0, September 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Apache 2.0

commercial

restricted free version is available

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

C, C++ and CUDA

Scala

C++

Rust

Server operating systems

Linux
OS X
Windows

Linux

Linux
Windows

Docker
Linux
macOS
Windows

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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

since Version 4.2

yes

Secondary indexes

yes

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

yes

APIs and other access methods

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

JDBC
ODBC

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

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

C
Java
Perl
Python
R

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

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

yes

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

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

depending on storage layer

Source-replica replication

yes, but depending on the SQL-Server Edition

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

Eventual Consistency, tunable 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.

depending on storage layer

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

fine grained access rights according to SQL-standard

Key-based authentication

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.