DBMS > EJDB vs. Sadas Engine vs. VictoriaMetrics vs. Vitess

System Properties Comparison EJDB vs. Sadas Engine vs. VictoriaMetrics vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Score	1.23
Rank	#172	Overall
	#15	Time Series DBMS

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

github.com/Softmotions/ejdb

www.sadasengine.com

victoriametrics.com

vitess.io

Technical documentation

github.com/Softmotions/ejdb/blob/master/README.md

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

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

vitess.io/docs

Developer

Softmotions

SADAS s.r.l.

VictoriaMetrics

The Linux Foundation, PlanetScale

Initial release

2012

2006

2018

2013

Current release

8.0

v1.91, May 2023

15.0.2, December 2022

License

Commercial or Open Source

Open Source

GPLv2

commercial

free trial version available

Open Source

Apache Version 2.0

Open Source

Apache Version 2.0, commercial licenses 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++

Server operating systems

server-less

AIX
Linux
Windows

FreeBSD
Linux
macOS
OpenBSD

Docker
Linux
macOS

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

yes

with proprietary extensions

APIs and other access methods

in-process shared library

JDBC
ODBC
Proprietary protocol

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

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
C
C#
C++
Groovy
Java
PHP
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

not for MyISAM storage engine

Transaction concepts

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

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

table locks or row locks depending on storage engine

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

managed by 'Learn by Usage'

yes

User concepts

Access control

Access rights for users, groups and roles according to SQL-standard

Users with fine-grained authorization concept

no user groups or 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

Recent citations in the news

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

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

VictoriaMetrics Slashes Data Storage Bills by 90% With World's Most Cost-Efficient Monitoring
30 May 2024, Yahoo Finance

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

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

provided by Google News

Share this page