DBMS > Coveo vs. Ignite vs. Sequoiadb vs. Tkrzw vs. Yaacomo

System Properties Comparison Coveo vs. Ignite vs. Sequoiadb 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

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

NewSQL database with distributed OLTP and SQL

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

Search engine

Key-value store
Relational DBMS

Document store
Relational DBMS

Key-value store

Relational DBMS

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

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	3.11
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	0.50
Rank	#258	Overall
	#41	Document stores
	#120	Relational DBMS

Score	0.07
Rank	#372	Overall
	#57	Key-value stores

Website

yaacomo.com

Technical documentation

docs.coveo.com

apacheignite.readme.io/docs

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

Coveo

Apache Software Foundation

Sequoiadb Ltd.

Mikio Hirabayashi

Q2WEB GmbH

Initial release

2012

2015

2013

2020

2009

Current release

Apache Ignite 2.6

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Server: AGPL; Client: Apache V2

Open Source

Apache Version 2.0

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++, Java, .Net

C++

Server operating systems

hosted

Linux
OS X
Solaris
Windows

Linux

Linux
macOS

Android
Linux
Windows

Data scheme

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

ANSI-99 for query and DML statements, subset of DDL

SQL-like query language

yes

APIs and other access methods

RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

proprietary protocol using JSON

JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Python

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C++
Java
PHP
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

JavaScript

Triggers

yes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes (replicated cache)

Source-replica replication

none

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

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

yes

ACID

Document is locked during a transaction

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.

yes

using specific database classes

yes

User concepts

Access control

granular access controls, API key management, content filters

Security Hooks for custom implementations

simple password-based access control

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

Recent citations in the news

Patrick Martin Sells 1531 Shares of Coveo Solutions Inc (TSE:CVO.TO) Stock
16 June 2024, Defense World

Is It Time To Consider Buying Coveo Solutions Inc. (TSE:CVO)?
6 June 2024, Yahoo Finance

Coveo Debuts GenAI Tools on Genesys Cloud and AppFoundry
17 May 2024, CX Today

Coveo Solutions Reports Strong Fiscal 2024 Results - TipRanks.com
3 June 2024, TipRanks

Coveo's 2024 Commerce Industry Report Finds More Than 70% of Consumers are Expecting Generative AI to ...
6 June 2024, PR Newswire

provided by Google News

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, PR Newswire

GridGain Showcases Power of Apache Ignite at Community Over Code Conference
5 October 2023, Datanami

Apache Ignite: Distributed Database
18 August 2015, ignite.apache.org

Apache Ignite: An Overview
6 September 2023, Open Source For You

What is Apache Ignite? How is Apache Ignite Used?
18 July 2022, The Stack

provided by Google News

Share this page