DBMS > Lovefield vs. searchxml vs. YottaDB

System Properties Comparison Lovefield vs. searchxml vs. YottaDB

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

DBMS for structured and unstructured content wrapped with an application server

A fast and solid embedded Key-value store

Primary database model

Relational DBMS

Native XML DBMS
Search engine

Key-value store

Secondary database models

Relational DBMS

using the Octo plugin

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

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	0.03
Rank	#390	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	0.28
Rank	#306	Overall
	#44	Key-value stores

Website

google.github.io/lovefield

www.searchxml.net/category/products

yottadb.com

Technical documentation

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

www.searchxml.net/support/handouts

yottadb.com/resources/documentation

Developer

Google

informationpartners gmbh

YottaDB, LLC

Initial release

2014

2015

2001

Current release

2.1.12, February 2017

1.0

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

AGPL 3.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

JavaScript

C++

Server operating systems

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

tested with Chrome, Firefox, IE, Safari

Windows

Docker
Linux

Data scheme

yes

schema-free

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

by using the Octo plugin

APIs and other access methods

RESTful HTTP API
WebDAV
XQuery
XSLT

PostgreSQL wire protocol

using the Octo plugin
Proprietary protocol

Supported programming languages

JavaScript

C++

most other programming languages supported via APIs

C
Go
JavaScript (Node.js)
Lua
M
Perl
Python
Rust

Server-side scripts

Stored procedures

yes

on the application server

Triggers

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

sychronisation to multiple collections

yes

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

yes

Transaction concepts

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

ACID

multiple readers, single writer

optimistic locking

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

User concepts

Access control

Domain, group and role-based access control at the document level and for application services

Users and groups based on OS-security mechanisms

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