DBMS > Cachelot.io vs. EJDB

System Properties Comparison Cachelot.io vs. EJDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

In-memory caching system

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

Primary database model

Key-value store

Document store

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

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Score	0.27
Rank	#297	Overall
	#44	Document stores

Website

cachelot.io

github.com/Softmotions/ejdb

Technical documentation

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

Developer

Softmotions

Initial release

2015

2012

License

Commercial or Open Source

Open Source

Simplified BSD License

Open Source

GPLv2

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

FreeBSD
Linux
OS X

server-less

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

SQL

Support of SQL

APIs and other access methods

Memcached protocol

in-process shared library

Supported programming languages

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
OCaml
Perl
PHP
Python
Ruby

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

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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.

User concepts

Access control

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.

Share this page