BitzOrcas currently uses IMemoryCache for specific infrastructure concerns. Application-level multi-tier caching with FusionCache is on the roadmap.
Current usage
| Use case | Implementation | Location |
|---|---|---|
| Idempotency | IMemoryCache | IdempotencyPipelineBehavior |
| Rate limiting | In-memory counters | ASP.NET Core RateLimiter |
Limitations
- Single-instance: In-memory caches don’t share across instances
- No eviction policy: IMemoryCache uses default LRU
- No distributed layer: No Redis/Valkey integration yet
Roadmap: FusionCache
Planned multi-tier caching:
┌─────────────────────────────┐│ Application ││ cache.Get/Set() │└─────────────┬───────────────┘ ▼┌─────────────────────────────┐│ FusionCache ││ ┌────────┐ ┌───────────┐ ││ │ L1 Mem │→ │ L2 Redis │ ││ └────────┘ └───────────┘ ││ + Stampede protection ││ + Fail-safe fallback ││ + OTel instrumentation │└─────────────────────────────┘See Caching building block for full details.