hp_hovercraft84
hp_hovercraft84 on Hacker News
Good call, but I think I would like to ensure it remains thread-safe as @store is a hash. Although I will consider something like this in a future update. Thanks!
This is why I love working with Ruby!
That's actually a really good idea! I'll definitely consider this in a future update. Thanks!
Good question. I built this gem because I needed a few things that Rails.cache (and Redis) didn’t quite fit:
- Local and zero-dependency. It caches per object in memory, so no Redis setup, no serialization, no network latency.
-Isolated and self-managed. Caches aren’t global. Each object/method manages its own LRU + TTL lifecycle and can be cleared with instance helpers.
- Easy to use — You just declare the method, set the TTL and max size, and you're done. No key names, no block wrapping, no external config.
As in identify where the source code is in the README?
Thanks for the feedback! That's a very good point, I'll update the gem and let it bubble up.
Posted by
hp_hovercraft84 on Tuesday April 22, 2025 @12:51PM
from the show-hn dept.
https://github.com/mishalzaman/memo_ttl
I built a Ruby gem for memoization with TTL + LRU cache. It’s thread-safe, and has been helpful in my own apps. Would love to get some feedback: https://github.com/mishalzaman/memo_ttl
No info about how the product works, immediate close.