DBMS > Faircom DB vs. Lovefield vs. Splunk vs. Tkrzw

System Properties Comparison Faircom DB vs. Lovefield vs. Splunk vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

Embeddable relational database for web apps written in pure JavaScript

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

Primary database model

Key-value store
Relational DBMS

Relational DBMS

Search engine

Key-value store

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

Score	0.30
Rank	#272	Overall
	#41	Key-value stores
	#126	Relational DBMS

Score	0.23
Rank	#286	Overall
	#134	Relational DBMS

Score	95.56
Rank	#14	Overall
	#2	Search engines

Score	0.00
Rank	#363	Overall
	#57	Key-value stores

Website

www.faircom.com/products/faircom-db

google.github.io/lovefield

www.splunk.com

dbmx.net/tkrzw

Technical documentation

learn.faircomcorp.com/developers/documentation_directory

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

docs.splunk.com/Documentation/Splunk

Developer

FairCom Corporation

Google

Splunk Inc.

Mikio Hirabayashi

Initial release

1979

2014

2003

2020

Current release

V12, November 2020

2.1.12, February 2017

0.9.3, August 2020

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache 2.0

commercial

Limited free edition and free developer edition available

Open Source

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

ANSI C, C++

JavaScript

C++

Server operating systems

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

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

tested with Chrome, Firefox, IE, Safari

Linux
OS X
Solaris
Windows

Linux
macOS

Data scheme

schema free, schema optional, schema required, partial schema,

yes

schema-free

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

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

yes, ANSI SQL with proprietary extensions

SQL-like query language

via JavaScript builder pattern

Splunk Search Processing Language for search commands

APIs and other access methods

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

HTTP REST

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

JavaScript

C#
Java
JavaScript
PHP
Python
Ruby

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

Triggers

yes

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

none

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

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

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Yes, tunable from durable to delayed durability to in-memory

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

User concepts

Access control

Fine grained access rights according to SQL-standard with additional protections for files

Access rights for users and roles

More information provided by the system vendor

Specific characteristics

Achieve Hundreds of Thousands of Transactions Per Second on A Single Database Server...
» more

Competitive advantages

Top Features SQL Key-value store and navigational NoSQL API Indexed binary objects...
» more

Typical application scenarios

Real-time transaction processing solutions leverage FairCom DB because its NoSQL...
» more

Key customers

Microsoft, UPS, Verizon, Motorola, Commvault, Thomson Reuters, ACI, BNY Mellon, Rockwell...
» more

Market metrics

From banking and financial transactions, transportation, warehouse automation, package...
» more

Licensing and pricing models

Just as the technical aspects of FairCom DB are flexible to meet operation requirements,...
» more

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