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. Minio vs Redis

Minio vs Redis

OverviewComparisonAlternatives

Overview

Redis
Redis
Stacks61.9K
Followers46.5K
Votes3.9K
GitHub Stars42
Forks6
Minio
Minio
Stacks637
Followers670
Votes43
GitHub Stars57.8K
Forks6.4K

Minio vs Redis: What are the differences?

Introduction:

In this document, we will discuss the key differences between Minio and Redis.

  1. Architecture: Minio is an object storage server that follows the S3 API, providing high-performance and scalable storage for unstructured data. It is designed to be self-hosted and can easily be deployed in a distributed setup. On the other hand, Redis is an in-memory data structure store that can be used as a database, cache, and message broker. It supports various data structures like strings, lists, sets, hashes, and more, and is known for its speed and versatility.

  2. Data Persistence: Minio stores objects durably in disk-based backends like RAID, NAS, or distributed File Systems. It provides fault-tolerance and high availability by replicating data across multiple drives or servers. In contrast, while Redis is primarily an in-memory database, it can also support persistence to disk. It offers different persistence modes, including snapshotting and append-only file (AOF) persistence, to ensure data persistence on disk.

  3. Data Manipulation: Minio allows users to store and retrieve large objects and files, making it suitable for applications that require storing multimedia files, backups, or data archives. It provides an S3-compatible RESTful API and SDKs in various programming languages for easy integration. On the other hand, Redis provides a rich set of data manipulation operations for the supported data structures. It is often used as a cache or a key-value store and supports atomic operations like incrementing a value or appending to a list.

  4. Scalability: Minio is designed to scale horizontally, allowing users to expand storage capacity by adding more drives or servers to the deployment. It can also distribute data across multiple servers using erasure coding for improved fault-tolerance and reduced storage overhead. Redis, on the other hand, can scale vertically by adding more memory to a single server or can be clustered to achieve horizontal scalability across multiple nodes.

  5. Data Replication: Minio supports data replication across multiple drives or servers to ensure data availability and fault tolerance. It allows users to define the replication factor and automatically replicates data to multiple drives or servers based on the chosen configuration. Redis, on the other hand, does not provide built-in data replication. However, it can be configured in a clustered mode to achieve data replication and high availability.

  6. Supported Data Types: Minio primarily deals with unstructured data, storing and retrieving objects and files. It follows the S3 API, enabling it to integrate seamlessly with applications that are built to work with S3-compatible storage. Redis, on the other hand, supports various structured and unstructured data types, including strings, lists, sets, sorted sets, hashes, bitmaps, and more. It provides specific data manipulation operations for each data type.

In summary, Minio is an object storage server focused on scalability, durability, and compatibility with the S3 API, while Redis is an in-memory data structure store known for its speed, versatility, and support for various data types. While Minio excels in handling large objects and provides fault-tolerant storage, Redis offers fast data manipulation and serves as a versatile cache or key-value store.

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

Redis
Redis
Minio
Minio

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.

Minio is an object storage server compatible with Amazon S3 and licensed under Apache 2.0 License

Statistics
GitHub Stars
42
GitHub Stars
57.8K
GitHub Forks
6
GitHub Forks
6.4K
Stacks
61.9K
Stacks
637
Followers
46.5K
Followers
670
Votes
3.9K
Votes
43
Pros & Cons
Pros
  • 888
    Performance
  • 542
    Super fast
  • 514
    Ease of use
  • 444
    In-memory cache
  • 324
    Advanced key-value cache
Cons
  • 15
    Cannot query objects directly
  • 3
    No secondary indexes for non-numeric data types
  • 1
    No WAL
Pros
  • 10
    Store and Serve Resumes & Job Description PDF, Backups
  • 8
    S3 Compatible
  • 4
    Simple
  • 4
    Open Source
  • 3
    Lambda Compute
Cons
  • 3
    Deletion of huge buckets is not possible
Integrations
No integrations available
Amazon S3
Amazon S3

What are some alternatives to Redis, Minio?

Amazon S3

Amazon S3

Amazon Simple Storage Service provides a fully redundant data storage infrastructure for storing and retrieving any amount of data, at any time, from anywhere on the web

Amazon EBS

Amazon EBS

Amazon EBS volumes are network-attached, and persist independently from the life of an instance. Amazon EBS provides highly available, highly reliable, predictable storage volumes that can be attached to a running Amazon EC2 instance and exposed as a device within the instance. Amazon EBS is particularly suited for applications that require a database, file system, or access to raw block level storage.

Google Cloud Storage

Google Cloud Storage

Google Cloud Storage allows world-wide storing and retrieval of any amount of data and at any time. It provides a simple programming interface which enables developers to take advantage of Google's own reliable and fast networking infrastructure to perform data operations in a secure and cost effective manner. If expansion needs arise, developers can benefit from the scalability provided by Google's infrastructure.

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.

Azure Storage

Azure Storage

Azure Storage provides the flexibility to store and retrieve large amounts of unstructured data, such as documents and media files with Azure Blobs; structured nosql based data with Azure Tables; reliable messages with Azure Queues, and use SMB based Azure Files for migrating on-premises applications to the cloud.

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

OpenEBS

OpenEBS

OpenEBS allows you to treat your persistent workload containers, such as DBs on containers, just like other containers. OpenEBS itself is deployed as just another container on your host.

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.

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