---
title: "Discussion on \"My Redis lock wasn't what kept deposit addresses unique\" | Hashnode"
description: "Discussion on \"My Redis lock wasn't what kept deposit addresses unique\". A fail-fast Redis lock, the Postgres row lock under it, Redis updates that wait for the commit, and a test that assumed Task.WhenAll means overlap."
url: "https://hashnode.com/posts/my-redis-lock-wasn-t-what-kept-deposit-addresses-unique/6acd011e374af6680337a694"
---

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

Discussion

# [My Redis lock wasn't what kept deposit addresses unique](https://agbad.hashnode.dev/my-redis-lock-wasn-t-what-kept-deposit-addresses-unique?utm_source=hashnode&utm_medium=feed)

A fail-fast Redis lock, the Postgres row lock under it, Redis updates that wait for the commit, and a test that assumed Task.WhenAll means overlap.

Oct 12 · 6 min read · agbad.hashnode.dev  
Read the article

-   [#redis](https://hashnode.com/tag/redis)
-   [#postgresql](https://hashnode.com/tag/postgresql)
-   [#dotnet](https://hashnode.com/tag/dotnet)
-   [#c-sharp](https://hashnode.com/tag/c-sharp)
-   [#distributed-systems](https://hashnode.com/tag/distributed-systems)

## Written by

[Damilare Agba](https://hashnode.com/@BlankGodd)

@BlankGodd

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

Backend & Blockchain Engineer

## Responses

Markdown supported · ⌘↵ to post

No responses yet.