DBMS > EJDB vs. InterSystems Caché vs. TimescaleDB vs. Yaacomo

System Properties Comparison EJDB vs. InterSystems Caché vs. TimescaleDB vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Caché is a deprecated database engine which is substituted with InterSystems IRIS. It therefore is removed from the DB-Engines Ranking.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

A multi-model DBMS and application server

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

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store

Key-value store
Object oriented DBMS
Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store

Relational DBMS

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

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

github.com/Softmotions/ejdb

www.intersystems.com/products/cache

www.timescale.com

yaacomo.com

Technical documentation

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

docs.intersystems.com

docs.timescale.com

Developer

Softmotions

InterSystems

Timescale

Q2WEB GmbH

Initial release

2012

1997

2017

2009

Current release

2018.1.4, May 2020

2.15.0, May 2024

License

Commercial or Open Source

Open Source

GPLv2

commercial

Open Source

Apache 2.0

commercial

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

AIX
HP Open VMS
HP-UX
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Android
Linux
Windows

Data scheme

schema-free

depending on used data model

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

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

Secondary indexes

yes

SQL

Support of SQL

yes

full PostgreSQL SQL syntax

yes

APIs and other access methods

in-process shared library

.NET Client API
JDBC
ODBC
RESTful HTTP API

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

JDBC
ODBC

Supported programming languages

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

C#
C++
Java

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

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

Partitioning methods

Methods for storing different data on different nodes

none

yes, across time and space (hash partitioning) attributes

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

Source-replica replication with hot standby and reads on replicas

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

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

Access rights for users, groups and roles

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

AWS, GCP, Oracle, Azure, SAP Lead Cloud DBMS Market: Gartner
12 February 2022, CRN

Epic On EHR Interoperability: Not A '1-Time Project'
10 April 2015, InformationWeek

Associative Data Modeling Demystified - Part1 - DataScienceCentral.com
9 July 2016, Data Science Central

Announcing IBM Spectrum Sentinel: Building a Cyber Resilient Future
24 June 2022, ibm.com

Choosing a Database Technology. A roadmap and process overview | by Shirish Joshi
23 February 2020, Towards Data Science

provided by Google News

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

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

Power IoT and time-series workloads with TimescaleDB for Azure Database for PostgreSQL
18 March 2019, Microsoft

Timescale Valuation Rockets to Over $1B with $110M Round, Marking the Explosive Rise of Time-Series Data
22 February 2022, Business Wire

Timescale announces $15M investment and new enterprise version of TimescaleDB
29 January 2019, TechCrunch

provided by Google News

Share this page