DBMS > Infobright vs. KeyDB vs. Lovefield vs. Splunk

System Properties Comparison Infobright vs. KeyDB vs. Lovefield vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

High performant column-oriented DBMS for analytic workloads using MySQL or PostgreSQL as a frontend

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Embeddable relational database for web apps written in pure JavaScript

Analytics Platform for Big Data

Primary database model

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

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	0.70
Rank	#229	Overall
	#32	Key-value stores

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	89.10
Rank	#14	Overall
	#2	Search engines

Website

ignitetech.com/softwarelibrary/infobrightdb

github.com/Snapchat/KeyDB
keydb.dev

google.github.io/lovefield

www.splunk.com

Technical documentation

docs.keydb.dev

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

docs.splunk.com/Documentation/Splunk

Developer

Ignite Technologies Inc.; formerly InfoBright Inc.

EQ Alpha Technology Ltd.

Google

Splunk Inc.

Initial release

2005

2019

2014

2003

Current release

2.1.12, February 2017

License

Commercial or Open Source

commercial

The open source (GPLv2) version did not support inserts/updates/deletes and was discontinued with July 2016

Open Source

BSD-3

Open Source

Apache 2.0

commercial

Limited free edition and free developer edition available

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

C++

JavaScript

Server operating systems

Linux
Windows

Linux

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

tested with Chrome, Firefox, IE, Safari

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

Knowledge Grid Technology used instead

yes

by using the Redis Search module

yes

SQL

Support of SQL

yes

SQL-like query language

via JavaScript builder pattern

Splunk Search Processing Language for search commands

APIs and other access methods

ADO.NET
JDBC
ODBC

Proprietary protocol

RESP - REdis Serialization Protoco

HTTP REST

Supported programming languages

.Net
C
C#
C++
D
Eiffel
Erlang
Haskell
Java
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

JavaScript

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

Lua

yes

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Multi-source replication
Source-replica replication

none

Multi-source 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
Strong eventual consistency with CRDTs

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Optimistic locking, atomic execution of commands blocks and scripts

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

Configurable mechanisms for persistency via snapshots and/or operations logs

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

User concepts

Access control

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

simple password-based access control and ACL

Access rights for users and roles

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

Recent citations in the news

Oh, snap! Snap snaps up database developer KeyDB
12 May 2022, TechCrunch

Garnet–open-source faster cache-store speeds up applications, services
18 March 2024, microsoft.com

Snap Acquires KeyDB for Open-Source Services
17 May 2022, XR Today

Microsoft open-sources Garnet cache-store -- a Redis rival?
19 March 2024, The Stack

Dragonfly 1.0 Released For What Claims To Be The World's Fastest In-Memory Data Store
20 March 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