DBMS > EJDB vs. FatDB vs. jBASE vs. TimescaleDB

System Properties Comparison EJDB vs. FatDB vs. jBASE vs. TimescaleDB

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

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

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

A robust multi-value DBMS comprising development tools and middleware

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

Primary database model

Document store

Document store
Key-value store

Multivalue 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.36
Rank	#157	Overall
	#3	Multivalue DBMS

Score	4.06
Rank	#73	Overall
	#5	Time Series DBMS

Website

github.com/Softmotions/ejdb

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

www.timescale.com

Technical documentation

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

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

docs.timescale.com

Developer

Softmotions

FatCloud

Rocket Software (formerly Zumasys)

Timescale

Initial release

2012

1991

2017

Current release

5.7

2.15.0, May 2024

License

Commercial or Open Source

Open Source

GPLv2

commercial

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

Server operating systems

server-less

Windows

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

optional

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

Via inetgration in SQL Server

Embedded SQL for jBASE in BASIC

yes

full PostgreSQL SQL syntax

APIs and other access methods

in-process shared library

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

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

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

.Net
Basic
Jabbascript
Java

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

via applications

yes

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

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

yes

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

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

User concepts

Access control

Can implement custom security layer via applications

Access rights can be defined down to the item level

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

Temenos signs first customer in India
24 August 2009, Finextra

provided by Google 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