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. Hazelcast vs Tarantool

Hazelcast vs Tarantool

OverviewComparisonAlternatives

Overview

Hazelcast
Hazelcast
Stacks427
Followers474
Votes59
GitHub Stars6.4K
Forks1.9K
Tarantool
Tarantool
Stacks32
Followers45
Votes9
GitHub Stars3.6K
Forks394

Hazelcast vs Tarantool: What are the differences?

What is Hazelcast? Clustering and highly scalable data distribution platform for Java. 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.

What is Tarantool? Free and open source an in-memory database and application server. 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.

Hazelcast and Tarantool can be categorized as "In-Memory Databases" tools.

Some of the features offered by Hazelcast are:

  • Distributed implementations of java.util.{Queue, Set, List, Map}
  • Distributed implementation of java.util.concurrent.locks.Lock
  • Distributed implementation of java.util.concurrent.ExecutorService

On the other hand, Tarantool provides the following key features:

  • Fast
  • Open source
  • Easy to use

Hazelcast and Tarantool are both open source tools. It seems that Hazelcast with 3.25K GitHub stars and 1.18K forks on GitHub has more adoption than Tarantool with 2.18K GitHub stars and 213 GitHub forks.

According to the StackShare community, Hazelcast has a broader approval, being mentioned in 35 company stacks & 81 developers stacks; compared to Tarantool, which is listed in 4 company stacks and 3 developer stacks.

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

Hazelcast
Hazelcast
Tarantool
Tarantool

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.

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

Distributed implementations of java.util.{Queue, Set, List, Map};Distributed implementation of java.util.concurrent.locks.Lock;Distributed implementation of java.util.concurrent.ExecutorService;Distributed MultiMap for one-to-many relationships;Distributed Topic for publish/subscribe messaging;Synchronous (write-through) and asynchronous (write-behind) persistence;Transaction support;Socket level encryption support for secure clusters;Second level cache provider for Hibernate;Monitoring and management of the cluster via JMX;Dynamic HTTP session clustering;Support for cluster info and membership events;Dynamic discovery, scaling, partitioning with backups and fail-over
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
Statistics
GitHub Stars
6.4K
GitHub Stars
3.6K
GitHub Forks
1.9K
GitHub Forks
394
Stacks
427
Stacks
32
Followers
474
Followers
45
Votes
59
Votes
9
Pros & Cons
Pros
  • 11
    High Availibility
  • 6
    Distributed compute
  • 6
    Distributed Locking
  • 5
    Sharding
  • 4
    Load balancing
Cons
  • 4
    License needed for SSL
Pros
  • 3
    Performance
  • 2
    Super fast
  • 2
    Open source
  • 1
    Advanced key-value cache
  • 1
    In-memory cache
Integrations
Java
Java
Spring
Spring
Node.js
Node.js
Perl
Perl
Java
Java
Python
Python
Golang
Golang
NGINX
NGINX
C#
C#

What are some alternatives to Hazelcast, Tarantool?

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.

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.

BuntDB

BuntDB

BuntDB is a low-level, in-memory, key/value store in pure Go. It persists to disk, is ACID compliant, and uses locking for multiple readers and a single writer. It supports custom indexes and geospatial data. It's ideal for projects that need a dependable database and favor speed over data size.

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