DBMS > ClickHouse vs. Lovefield vs. Manticore Search

System Properties Comparison ClickHouse vs. Lovefield vs. Manticore Search

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Column-oriented Relational DBMS powering Yandex

Embeddable relational database for web apps written in pure JavaScript

Multi-storage database for search, including full-text search.

Primary database model

Relational DBMS

Search engine

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	15.13
Rank	#39	Overall
	#24	Relational DBMS

Score	0.58
Rank	#273	Overall
	#123	Relational DBMS

Score	0.23
Rank	#346	Overall
	#22	Search engines

Website

clickhouse.com

google.github.io/lovefield

manticoresearch.com

Technical documentation

clickhouse.com/docs

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

manual.manticoresearch.com

Developer

Clickhouse Inc.

Google

Manticore Software

Initial release

2016

2014

2017

Current release

v23.7.4.5-stable, August 2023

2.1.12, February 2017

6.0, February 2023

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

Apache 2.0

Open Source

GPL version 2

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.

Aiven for Clickhouse: Managed cloud data warehousing with high-speed analytics.

Implementation language

C++

JavaScript

C++

Server operating systems

FreeBSD
Linux
macOS

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

tested with Chrome, Firefox, IE, Safari

FreeBSD
Linux
macOS
Windows

Data scheme

yes

Fixed schema

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

Secondary indexes

yes, when using the MergeTree engine

yes

full-text index on all search fields

SQL

Support of SQL

Close to ANSI SQL

SQL-like query language

via JavaScript builder pattern

SQL-like query language

APIs and other access methods

HTTP REST
JDBC
ODBC
Proprietary protocol

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

Supported programming languages

3rd party library
C++
Elixir

3rd party library
Go

3rd party library
Java

3rd party library
JavaScript (Node.js)

3rd party library
Kotlin

3rd party library
Nim

3rd party library
Perl

3rd party library
PHP

3rd party library
Python

3rd party library
R

3rd party library
Ruby

3rd party library
Scala

3rd party library

JavaScript

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Server-side scripts

Stored procedures

user defined functions

Triggers

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

none

Synchronous replication based on Galera library

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

yes

isolated transactions for atomic changes and binary logging for safe writes

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

yes

The original contents of fields are not stored in the Manticore index.

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

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.