StackShareStackShare
Follow on
StackShare

Discover and share technology stacks from companies around the world.

Follow on

© 2025 StackShare. All rights reserved.

Product

  • Stacks
  • Tools
  • Feed

Company

  • About
  • Contact

Legal

  • Privacy Policy
  • Terms of Service
  1. Stackups
  2. Application & Data
  3. In-Memory Databases
  4. In Memory Databases
  5. CQEngine vs Tarantool

CQEngine vs Tarantool

OverviewComparisonAlternatives

Overview

Tarantool
Tarantool
Stacks32
Followers45
Votes9
GitHub Stars3.6K
Forks394
CQEngine
CQEngine
Stacks3
Followers22
Votes0
GitHub Stars1.8K
Forks255

CQEngine vs Tarantool: What are the differences?

Introduction

Below are the key differences between CQEngine and Tarantool.

  1. Primary Use Case: CQEngine is a Java library for indexing and searching collections efficiently, providing features for querying in-memory collections. On the other hand, Tarantool is an in-memory database and application server that can also function as a cache or a message queue.

  2. Language Compatibility: CQEngine is specifically designed for Java applications, making it suitable for projects developed in Java. In contrast, Tarantool supports multiple programming languages such as Lua, Python, C, and C++, offering flexibility for developers with different language preferences.

  3. Persistence Mechanism: CQEngine primarily focuses on in-memory data storage and retrieval, operating solely in-memory without persistence to disk. In contrast, Tarantool provides both in-memory and on-disk storage options, offering persistent data storage for durability.

  4. Concurrency Control: CQEngine does not provide built-in support for concurrent read and write access to collections, requiring developers to implement their synchronization mechanisms. On the flip side, Tarantool comes with built-in support for multi-version concurrency control (MVCC), enabling concurrent access to data with consistent results.

  5. Data Replication: CQEngine does not include built-in support for data replication across multiple nodes, making it more suitable for standalone applications. Meanwhile, Tarantool offers seamless data replication capabilities, allowing for distributed deployments and high availability configurations.

  6. Extensions and Plugins: CQEngine is primarily a lightweight library with limited extension points, while Tarantool provides an extensive set of APIs and plugins for developers to extend its functionality, facilitating customizations and integrations with various systems.

In Summary, CQEngine and Tarantool differ in their primary use cases, language compatibility, persistence mechanisms, concurrency control, data replication capabilities, and extension/plugin support.

Share your Stack

Help developers discover the tools you use. Get visibility for your team's tech choices and contribute to the community's knowledge.

View Docs
CLI (Node.js)
or
Manual

Detailed Comparison

Tarantool
Tarantool
CQEngine
CQEngine

It is designed to give you the flexibility, scalability, and performance that you want, as well as the reliability and manageability that you need in mission-critical applications

It is a NoSQL indexing and Query Engine, for retrieving objects matching SQL-like queries from Java collections, with ultra-low latency

Fast; Open source; Easy to use;Multiple index types: HASH, TREE, RTREE, BITSET;Asynchronous master-master replication;Authentication and access control;The database is just a C extension to the application server and can be turned off
Ultra-fast; Query engine; No SQL
Statistics
GitHub Stars
3.6K
GitHub Stars
1.8K
GitHub Forks
394
GitHub Forks
255
Stacks
32
Stacks
3
Followers
45
Followers
22
Votes
9
Votes
0
Pros & Cons
Pros
  • 3
    Performance
  • 2
    Open source
  • 2
    Super fast
  • 1
    In-memory cache
  • 1
    Advanced key-value cache
No community feedback yet
Integrations
Node.js
Node.js
Perl
Perl
Java
Java
Python
Python
Golang
Golang
NGINX
NGINX
C#
C#
MongoDB
MongoDB
PostgreSQL
PostgreSQL
Fastify
Fastify
MySQL
MySQL

What are some alternatives to Tarantool, CQEngine?

Redis

Redis

Redis is an open source (BSD licensed), in-memory data structure store, used as a database, cache, and message broker. Redis provides data structures such as strings, hashes, lists, sets, sorted sets with range queries, bitmaps, hyperloglogs, geospatial indexes, and streams.

Hazelcast

Hazelcast

With its various distributed data structures, distributed caching capabilities, elastic nature, memcache support, integration with Spring and Hibernate and more importantly with so many happy users, Hazelcast is feature-rich, enterprise-ready and developer-friendly in-memory data grid solution.

Aerospike

Aerospike

Aerospike is an open-source, modern database built from the ground up to push the limits of flash storage, processors and networks. It was designed to operate with predictable low latency at high throughput with uncompromising reliability – both high availability and ACID guarantees.

MemSQL

MemSQL

MemSQL converges transactions and analytics for sub-second data processing and reporting. Real-time businesses can build robust applications on a simple and scalable infrastructure that complements and extends existing data pipelines.

Apache Ignite

Apache Ignite

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

SAP HANA

SAP HANA

It is an application that uses in-memory database technology that allows the processing of massive amounts of real-time data in a short time. The in-memory computing engine allows it to process data stored in RAM as opposed to reading it from a disk.

VoltDB

VoltDB

VoltDB is a fundamental redesign of the RDBMS that provides unparalleled performance and scalability on bare-metal, virtualized and cloud infrastructures. VoltDB is a modern in-memory architecture that supports both SQL + Java with data durability and fault tolerance.

Azure Redis Cache

Azure Redis Cache

It perfectly complements Azure database services such as Cosmos DB. It provides a cost-effective solution to scale read and write throughput of your data tier. Store and share database query results, session states, static contents, and more using a common cache-aside pattern.

KeyDB

KeyDB

KeyDB is a fully open source database that aims to make use of all hardware resources. KeyDB makes it possible to breach boundaries often dictated by price and complexity.

LokiJS

LokiJS

LokiJS is a document oriented database written in javascript, published under MIT License. Its purpose is to store javascript objects as documents in a nosql fashion and retrieve them with a similar mechanism. Runs in node (including cordova/phonegap and node-webkit), nativescript and the browser.

Related Comparisons

Bootstrap
Materialize

Bootstrap vs Materialize

Laravel
Django

Django vs Laravel vs Node.js

Bootstrap
Foundation

Bootstrap vs Foundation vs Material UI

Node.js
Spring Boot

Node.js vs Spring-Boot

Liquibase
Flyway

Flyway vs Liquibase