RTS Questionnaire · Question 05 of 52 · file: answers/q05.html
Have you worked with caching technologies such as Redis or Memcached?
RedisCachingPerformance
✅ Yes — distributed caching is a standard part of my architecture toolkit, with Redis as the primary technology.
🧪 Interactive proof: this answer has its own page with a live cache workflow, the code behind it and the acceptance criteria — open the Q05 caching proof →
Technical detail
- 🔴 Redis — listed among my core data technologies: cache-aside and write-through patterns, key naming/TTL strategy, eviction policies (LRU/LFU), hashes and sorted sets for leaderboards and counters, pub/sub and streams for lightweight events, distributed locks for coordination, and Redis Cluster/Sentinel thinking for high availability.
- 🧰 Application-level integration —
StackExchange.RedisandIDistributedCachein .NET, Spring Cache with@Cacheable/@CacheEvict, and Node.js/FastAPI clients; plus in-processIMemoryCache/memoisation for the hot in-node layer. - 🟦 Memcached — same key/value cache-aside model, understood for simple multi-node object caching where a slim, non-persistent store is enough.
- 🌐 Edge and HTTP caching — CDN/CloudFront-style caching, response caching, ETag/conditional requests and cache-busting strategies for static assets and API responses.
📊 The engineering discipline I apply: always define the invalidation contract before adding a cache, measure hit ratio and p95 latency, protect the database from stampedes with jittered TTLs and single-flight locking, and never let stale data silently break business rules. 🧪 Cache behaviour is covered by tests and load checks.
🧾 CV evidence: 2025/2026 CV technology list includes Redis under databases; AWS non-relational and data services profile (DynamoDB, ElastiCache-style patterns); performance-tuning competencies listed under Architectural competencies in the CV.