rueidis VS go-deadlock

I have a redis client library which code base is small while it uses some advanced techniques to achieve better performance. I think it is worth reading https://github.com/rueian/rueidis

Want to say +1 for Rueidis. It's a very fast, well-maintained library. It's already adopted by several large open-source projects (see https://github.com/rueian/rueidis/network/dependents). Nothing to say against go-redis though - it's very good too.

Hi folks, I am pleased to introduce you rueidis v0.0.90, a Redis client library that can help you access Redis server with little or almost zero allocation on your application side.

Hi rtsov, I also like to have this kind of amqp functionality in rueidis https://github.com/rueian/rueidis.

You can also use redis to store sessions remotely, and use its client-side caching feature for better performance: https://github.com/rueian/rueidis

All these help me build a fast redis client library: https://github.com/rueian/rueidis

Use redis+client-side caching to implement your replicas. This can help you: https://github.com/rueian/rueidis

Actually it is also beneficial for applications using redis for distributed locks magement. Redis can now notify clients the state of their locks proactively. https://github.com/rueian/rueidis/tree/master/rueidislock

rueidis For fast client-side caching, distributed locking and Pub/Sub with Redis.

sasha-s/go-deadlock: online deadlock detection in go

Not quite an answer but this helped with the headache of debugging deadlocks for our team https://github.com/sasha-s/go-deadlock Its a drop in replacement and will error out when it detects deadlocks.

A truly underrated static analyzer in Go is github.com/sasha-s/go-deadlock

go-deadlock library

No mention of go-deadlock? It's amazing tool that will save you so much time. I found a lot of lock-ordering issues that were just disasters waiting to happen.