There is a library in Go — LRU, where you can pass Any and set TTL. Why was Redis chosen instead of it?

The choice of Redis instead of a local LRU library with TTL in Go is due to several reasons:

• Distribution: Redis is a separate server accessible from different applications and services, allowing centralized caching.
• Resilience and scalability: Redis supports replication, clustering, and is fault-tolerant, whereas a local LRU library stores data only in the memory of a single process.
• Rich functionality: Redis provides many data structures, TTL operations, atomic operations, and monitoring.
• Separation of state from the application: When the application restarts, the local cache is lost, whereas Redis can retain data longer.

Thus, Redis is suitable for caching in distributed systems and under high loads, while an LRU library is convenient for simple cases and local caching.