---
title: "Discussion on \"Why Slack Redesigned Their Job Queue\" | Hashnode"
description: "Discussion on \"Why Slack Redesigned Their Job Queue\". Understand the architecture constraints Slack identified while using Redis as a message queue."
url: "https://hashnode.com/posts/why-slack-redesigned-their-job-queue/65db329e0f630ae588ae7e45"
---

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

Discussion

# [Why Slack Redesigned Their Job Queue](https://zahere.com/why-slack-redesigned-their-job-queue?utm_source=hashnode&utm_medium=feed)

Understand the architecture constraints Slack identified while using Redis as a message queue.

Feb 25, 2024 · 5 min read · zahere.com  
Read the article

-   [#system-design](https://hashnode.com/tag/system-design)
-   [#system-architecture](https://hashnode.com/tag/system-architecture)
-   [#architecture](https://hashnode.com/tag/architecture)
-   [#redis](https://hashnode.com/tag/redis)
-   [#pubsub](https://hashnode.com/tag/pubsub)
-   [#message-queue](https://hashnode.com/tag/message-queue)

## Written by

[Zahiruddin Tavargere](https://hashnode.com/@Zahere)

@Zahere · Bengaluru

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

Learning to learn

I am a Journalist-turned-Software Engineer. I love coding and the associated grind of learning every day. A firm believer in social learning, I owe my dev career to all the tech content creators I have learned from. This is my contribution back to the community.

## Responses

Markdown supported · ⌘↵ to post

No responses yet.
