DBMS > Elasticsearch vs. FatDB vs. Infobright vs. Machbase Neo

System Properties Comparison Elasticsearch vs. FatDB vs. Infobright vs. Machbase Neo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

TimeSeries DBMS for AIoT and BigData

Primary database model

Search engine

Document store
Key-value store

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	132.83
Rank	#7	Overall
	#1	Search engines

Score	1.02
Rank	#192	Overall
	#90	Relational DBMS

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Website

www.elastic.co/elasticsearch

ignitetech.com/softwarelibrary/infobrightdb

machbase.com

Technical documentation

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

machbase.com/dbms

Developer

Elastic

FatCloud

Ignite Technologies Inc.; formerly InfoBright Inc.

Machbase

Initial release

2010

2012

2005

2013

Current release

8.6, January 2023

V8.0, August 2023

License

Commercial or Open Source

Open Source

Elastic License

commercial

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

commercial

free test version 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

Java

Server operating systems

All OS with a Java VM

Windows

Linux
Windows

Linux
macOS
Windows

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

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.

Secondary indexes

yes

All search fields are automatically indexed

yes

Knowledge Grid Technology used instead

yes

SQL

Support of SQL

SQL-like query language

Via inetgration in SQL Server

yes

SQL-like query language

APIs and other access methods

Java API
RESTful HTTP/JSON API

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

ADO.NET
JDBC
ODBC

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

Supported programming languages

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

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

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

Server-side scripts

Stored procedures

yes

via applications

Triggers

yes

by using the 'percolation' feature

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

Source-replica replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Memcached and Redis integration

yes

volatile and lookup table

User concepts

Access control

Can implement custom security layer via applications

fine grained access rights according to SQL-standard

exploiting MySQL or PostgreSQL frontend capabilities

simple password-based access control

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

PostgreSQL is the DBMS of the Year 2017
2 January 2018, Paul Andlinger, Matthias Gelbmann

Elasticsearch moved into the top 10 most popular database management systems
3 July 2017, Matthias Gelbmann

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

Recent citations in the news

8 Powerful Alternatives to Elasticsearch
25 April 2024, Yahoo Finance

Splunk vs Elasticsearch | A Comparison and How to Choose
12 January 2024, SentinelOne

Introducing Elasticsearch Vector Database to Azure OpenAI Service On Your Data (Preview)
26 March 2024, GovTech

Netflix Uses Elasticsearch Percolate Queries to Implement Reverse Searches Efficiently
29 April 2024, InfoQ.com

Elasticsearch Open Inference API Supports Cohere Rerank 3
11 April 2024, Business Wire

provided by Google News

Share this page