DBMS > Lovefield vs. searchxml vs. Splunk vs. Tkrzw vs. Yaacomo

System Properties Comparison Lovefield vs. searchxml vs. Splunk vs. Tkrzw vs. Yaacomo

Editorial information provided by DB-Engines

Name

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

Description

Embeddable relational database for web apps written in pure JavaScript

DBMS for structured and unstructured content wrapped with an application server

Analytics Platform for Big Data

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

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

Primary database model

Relational DBMS

Native XML DBMS
Search engine

Search engine

Key-value store

Relational DBMS

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

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	86.45
Rank	#14	Overall
	#2	Search engines

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

Website

google.github.io/lovefield

www.searchxml.net/category/products

www.splunk.com

dbmx.net/tkrzw

yaacomo.com

Technical documentation

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

www.searchxml.net/support/handouts

docs.splunk.com/Documentation/Splunk

Developer

Google

informationpartners gmbh

Splunk Inc.

Mikio Hirabayashi

Q2WEB GmbH

Initial release

2014

2015

2003

2020

2009

Current release

2.1.12, February 2017

1.0

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Limited free edition and free developer edition available

Open Source

Apache Version 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

JavaScript

C++

Server operating systems

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

tested with Chrome, Firefox, IE, Safari

Windows

Linux
OS X
Solaris
Windows

Linux
macOS

Android
Linux
Windows

Data scheme

yes

schema-free

yes

schema-free

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

Splunk Search Processing Language for search commands

yes

APIs and other access methods

RESTful HTTP API
WebDAV
XQuery
XSLT

HTTP REST

JDBC
ODBC

Supported programming languages

JavaScript

C++

most other programming languages supported via APIs

C#
Java
JavaScript
PHP
Python
Ruby

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

on the application server

yes

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

sychronisation to multiple collections

Multi-source replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

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

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

ACID

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

using specific database classes

yes

User concepts

Access control

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

Access rights for users 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

DB-Engines blog posts

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger

show all

Share this page