DBMS > Lovefield vs. MarkLogic vs. SAP HANA vs. Transbase

System Properties Comparison Lovefield vs. MarkLogic vs. SAP HANA vs. Transbase

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Embeddable relational database for web apps written in pure JavaScript

Operational and transactional Enterprise NoSQL database

In-memory, column based data store. Available as appliance or cloud service

A resource-optimized, high-performance, universally applicable RDBMS

Primary database model

Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	5.18
Rank	#63	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#7	Search engines

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

google.github.io/lovefield

www.progress.com/marklogic

www.sap.com/products/hana.html

www.transaction.de/en/products/transbase.html

Technical documentation

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

www.progress.com/marklogic/documentation

help.sap.com/hana

www.transaction.de/en/products/transbase/features.html

Developer

Google

MarkLogic Corp.

SAP

Transaction Software GmbH

Initial release

2014

2001

2010

1987

Current release

2.1.12, February 2017

11.0, December 2022

2.0 SPS07 (April 4, 2023), April 2023

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

restricted free version is available

commercial

free development license

Cloud-based only

Only available as a cloud service

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

JavaScript

C++

C and C++

Server operating systems

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

tested with Chrome, Firefox, IE, Safari

Linux
OS X
Windows

Appliance or cloud-service

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

schema-free

Schema can be enforced

yes

Typing

predefined data types such as float or date

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

SQL-like query language

via JavaScript builder pattern

yes

SQL92

yes

APIs and other access methods

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

JavaScript

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

SQLScript, R

yes

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

can act as a resource manager in an XA/JTA transaction

ACID

yes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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

yes

In-memory capabilities

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

yes

using MemoryDB

yes, with Range Indexes

yes

User concepts

Access control

Role-based access control at the document and subdocument levels

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.