---
title: "Discussion on \"My Backend Crashed Every Time Redis Went Down. Three Patterns Fixed That.\" | Hashnode"
description: "Discussion on \"My Backend Crashed Every Time Redis Went Down. Three Patterns Fixed That.\". In Part 11, I built a metrics system to see the big picture — request counts, latencies, error rates per endpoint.\nThen I looked at my main.go and realized something embarrassing. The JWT secret was hardcoded. The Redis address was a string literal. ..."
url: "https://hashnode.com/posts/my-backend-crashed-every-time-redis-went-down-three-patterns-fixed-that/69f2171e545cd046ab6aad5e"
---

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

Discussion

# [My Backend Crashed Every Time Redis Went Down. Three Patterns Fixed That.](https://abhishekshr.hashnode.dev/my-backend-crashed-every-time-redis-went-down-three-patterns-fixed-that?utm_source=hashnode&utm_medium=feed)

In Part 11, I built a metrics system to see the big picture — request counts, latencies, error rates per endpoint. Then I looked at my main.go and realized something embarrassing. The JWT secret was hardcoded. The Redis address was a string literal. ...

Apr 29 · 8 min read · abhishekshr.hashnode.dev  
Read the article

-   [#backend](https://hashnode.com/tag/backend)
-   [#buildinpublic](https://hashnode.com/tag/buildinpublic)
-   [#go](https://hashnode.com/tag/go)
-   [#resilience](https://hashnode.com/tag/resilience)

## Written by

[Abhishek Sharma](https://hashnode.com/@abhishekshr)

@abhishekshr

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

## Responses

Markdown supported · ⌘↵ to post

No responses yet.