PrototypeCommon
seamusabshere/lock_and_cache
Most caching libraries don't do locking, meaning that >1 process can be calculating a cached value at the same time. Since you presumably cache things because they cost CPU, database reads, or money, doesn't it make sense to lock while caching?
- Owner
- seamusabshere (personal account)
- Stars
- Stars: 133
- Forks
- Forks: 5
- Language
- Ruby
- License
- MIT
- Created
- 2014
- Tier
- Prototype (100 to 249 ★) What this tier means
More repos by seamusabshere
All 7 repos by seamusabshere- seamusabshere/fuzzy_matchStars: 686RubyAlpha
- seamusabshere/upsertStars: 646RubyAlpha
- seamusabshere/data_minerStars: 305RubyAlpha
- seamusabshere/remote_tableStars: 228HTMLPrototype
- seamusabshere/unix_utilsStars: 225RubyPrototype
- seamusabshere/cache_methodStars: 136RubyPrototype
Nearby in Ruby
All Ruby repos- LizardByte/homebrew-homebrewStars: 133RubyPrototype
- dreamwords/hammer-releasesStars: 133RubyPrototype
- basecamp/hotcellStars: 133RubyPrototype
- floere/jamesStars: 133RubyPrototype
- springbok/smerfStars: 133RubyPrototype
- wvanbergen/adyenStars: 133RubyPrototype