jellydator/ttlcache
An in-memory cache with item expiration and generics observed · 2026-08-28
Health v2 · maintenance only
84/100
- Activity 98
- Release rhythm 57
- Longevity 100
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: 369
- age_days: 4282
- days_rel: 72
- days_push: 12
- n_releases_24m: 2
Adoption not part of the score
1278 stars · 145 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-30, confidence not recorded
TTLCache is an in-memory cache library for Go with per-item or cache-wide TTL expiration, built using generics. It offers thread-safe operations, capacity limits, lazy loading, event handlers, and metrics.
Use cases
- cache api responses in memory with expiration
- add a ttl-based cache to a go service
- limit cache size by item count or cost
- lazily load missing cache values with duplicate suppression
- track cache hits and misses with metrics
- run eviction callbacks when items expire
When to choose
- you need a lightweight in-process cache with TTL expiration in Go
- you want generics-based type safety without interface{} casts
- you need capacity limits, loaders, or eviction event hooks
When to avoid
- you need a distributed or shared cache across multiple instances (use Redis)
- your dataset exceeds available memory
- you need persistence or eviction across process restarts
Facets
library · maturity active
caching developer-tools backend performance go ttl-cache in-memory-cache generics thread-safe lru-alternative
1 source
- readme: https://github.com/jellydator/ttlcache · fetched 2026-08-28 · efdb4f47375f
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| jellydator/ttlcache | main | 84 |
For agents
markdown · JSON · MCP: product_card(name="jellydator/ttlcache")
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem