---
title: "Discussion on \"Sharding, Replication, and Sharded Replication in Redis\" | Hashnode"
description: "Discussion on \"Sharding, Replication, and Sharded Replication in Redis\". verything so far has assumed a single Redis instance. That's fine for a lot of use cases, but it has two hard limits: your dataset can't be bigger than one machine's RAM, and if that one machine goes"
url: "https://hashnode.com/posts/sharding-replication-and-sharded-replication-in-redis/6a51a4e956d3e49909261961"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Sharding, Replication, and Sharded Replication in Redis](https://syntax-soul.hashnode.dev/sharding-replication-and-sharded-replication-in-redis?utm_source=hashnode&utm_medium=feed)

verything so far has assumed a single Redis instance. That's fine for a lot of use cases, but it has two hard limits: your dataset can't be bigger than one machine's RAM, and if that one machine goes

Jul 11 · 11 min read · syntax-soul.hashnode.dev  
Read the article

-   [#sharding](https://hashnode.com/tag/sharding)
-   [#caching](https://hashnode.com/tag/caching)
-   [#replication](https://hashnode.com/tag/replication)
-   [#redis](https://hashnode.com/tag/redis)
-   [#redis-cache](https://hashnode.com/tag/redis-cache)

## Written by

[Mayank Jain](https://hashnode.com/@mayankj)

@mayankj · Delhi, India

  
[View profile](https://hashnode.com/@mayankj)

## Responses

Markdown supported · ⌘↵ to post

No responses yet.