DBMS > Apache IoTDB vs. EJDB vs. Linter vs. Lovefield

System Properties Comparison Apache IoTDB vs. EJDB vs. Linter vs. Lovefield

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An IoT native database with high performance for data management and analysis, deployable on the edge and the cloud and integrated with Hadoop, Spark and Flink

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

RDBMS for high security requirements

Embeddable relational database for web apps written in pure JavaScript

Primary database model

Time Series DBMS

Document store

Relational DBMS

Secondary database models

Spatial DBMS

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

Score	1.31
Rank	#164	Overall
	#14	Time Series DBMS

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	0.12
Rank	#350	Overall
	#152	Relational DBMS

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Website

iotdb.apache.org

github.com/Softmotions/ejdb

linter.ru

google.github.io/lovefield

Technical documentation

iotdb.apache.org/UserGuide/Master/QuickStart/QuickStart.html

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

github.com/google/lovefield/blob/master/docs/spec_index.md

Developer

Apache Software Foundation

Softmotions

relex.ru

Google

Initial release

2018

2012

1990

2014

Current release

1.1.0, April 2023

2.1.12, February 2017

License

Commercial or Open Source

Open Source

Apache Version 2.0

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

Java

C and C++

JavaScript

Server operating systems

All OS with a Java VM (>= 1.8)

server-less

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Data scheme

yes

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

SQL-like query language

yes

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

JDBC
Native API

in-process shared library

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

Supported programming languages

C
C#
C++
Go
Java
Python
Scala

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

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

JavaScript

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by time range) + vertical partitioning (by deviceId)

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication methods; using Raft/IoTConsensus algorithm to ensure strong/eventual data consistency among multiple replicas

none

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Integration with Hadoop and Spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong Consistency with Raft

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

yes, by using IndexedDB or the cloud service Firebase Realtime Database

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

using MemoryDB

User concepts

Access control

yes

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

AMD EPYC 4364P & 4564P @ DDR5-4800 / DDR5-5200 vs. Intel Xeon E-2488 Review
6 June 2024, Phoronix

TsFile: A Standard Format for IoT Time Series Data
27 February 2024, The New Stack

Linux 6.5 With AMD P-State EPP Default Brings Performance & Power Efficiency Benefits For Ryzen Servers
21 September 2023, Phoronix

Apache Promotes IoT Database Project
25 September 2020, Datanami

AMD EPYC 8324P / 8324PN Siena 32-Core Siena Linux Server Performance Review
10 October 2023, Phoronix

provided by Google News

Kagiso interactive shares: all eyes on android at google I/O
11 May 2015, WhaTech

provided by Google News

Share this page