DBMS > EJDB vs. GBase vs. Machbase Neo vs. TimescaleDB

System Properties Comparison EJDB vs. GBase vs. Machbase Neo vs. TimescaleDB

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)

Widely used RDBMS in China, including analytical, transactional, distributed transactional, and cloud-native data warehousing.

TimeSeries DBMS for AIoT and BigData

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Document store

Relational DBMS

Time Series DBMS

Secondary database models

Relational DBMS

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

Score	0.13
Rank	#331	Overall
	#46	Document stores

Score	1.11
Rank	#173	Overall
	#78	Relational DBMS

Score	0.07
Rank	#348	Overall
	#34	Time Series DBMS

Score	4.06
Rank	#73	Overall
	#5	Time Series DBMS

Website

github.com/Softmotions/ejdb

www.gbase.cn

machbase.com

www.timescale.com

Technical documentation

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

machbase.com/dbms

docs.timescale.com

Developer

Softmotions

General Data Technology Co., Ltd.

Machbase

Timescale

Initial release

2012

2004

2013

2017

Current release

GBase 8a, GBase 8s, GBase 8c

V8.0, August 2023

2.15.0, May 2024

License

Commercial or Open Source

Open Source

GPLv2

commercial

free test version available

Open Source

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

Implementation language

C, Java, Python

Server operating systems

server-less

Linux

Linux
macOS
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

Secondary indexes

yes

SQL

Support of SQL

Standard with numerous extensions

SQL-like query language

yes

full PostgreSQL SQL syntax

APIs and other access methods

in-process shared library

ADO.NET
C API
JDBC
ODBC

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

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

Supported programming languages

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

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning (by range, list and hash) and vertical partitioning

Sharding

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

selectable replication factor

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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

yes

simple password-based access control

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.

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

General availability: Latest version of the TimeScaleDB extension on Azure Database for PostgreSQL - Flexible Server
8 May 2024, Microsoft

Timescale Acquires PopSQL to Bring a Modern, Collaborative SQL GUI to PostgreSQL Developers
4 April 2024, PR Newswire

TimescaleDB Is a Vector Database Now, Too
25 September 2023, Datanami

PostgreSQL is Now Faster than Pinecone, 75% Cheaper, with New Open Source Extensions
11 June 2024, PR Newswire

Understanding Hyperfunctions in TimescaleDB
11 August 2021, CDOTrends

provided by Google News

Share this page