← All 186 courses
CL-322 Cloud & Platform

Caching & Data Access Performance

Cut data access latency with caching that survives invalidation, expiry and traffic spikes. Learners implement cache-aside and write-through paths over Redis, choose TTL and eviction policies from real staleness tolerance, defend against stampedes and hot keys, and prove the gain with hit ratio measured against p99 latency rather than a comforting percentage.

B3Practitioner
5modules
35skill atoms
2role journeys
Curriculum

What this course covers.

5 modules, 35 named skill atoms. Expand any module to see them.

1Cache Placement and Patterns7 skill atoms
cache-aside as the default read pathread-through and write-through trade-offswrite-behind and its durability riskclient, application and CDN layer placementcaching a computation against caching a rowwhat must never be cachedRedis data types matched to access pattern
2TTL, Eviction and Memory7 skill atoms
TTL chosen from tolerance for stalenessallkeys-lru, volatile-ttl and noeviction policieseviction surfacing as a sudden hit ratio dropfragmentation and used_memory_rsskey and value size disciplineexpiry sampling and lazy deletionINFO memory and keyspace statistics
3Invalidation Strategies7 skill atoms
explicit delete on writeversioned key namespaces for bulk invalidationTTL as the safety net behind explicit invalidationpub/sub invalidation across instancesdatabase change events driving invalidationstale reads during the invalidation gapcaching negative results with care
4Stampedes, Hot Keys and Locks7 skill atoms
thundering herd on a cold or expired keyprobabilistic early expirationrequest coalescing and single-flighta hot key saturating one shardkey sharding and local in-process cachesdistributed locks with SET NX and expiryRedlock hazards and lock expiry mid-work
5Measuring Real Gains7 skill atoms
hit ratio measured per key family not globallyp50, p95 and p99 latency before and aftercaching a query that was never sloworigin load reduction as the honest metricRedis slowlog and latency doctorconnection pool exhaustion under loadbehaviour when the cache is entirely down
Where it fits

CL-322 in the role journeys.

This course appears in 2 of our 45 role journeys. Here is what a learner takes immediately before and after it in each.

Cloud Engineer

Practitioner stage
CL-205CL-322CL-311

Site Reliability Engineer

Practitioner stage
CL-403CL-322CL-402

Roles this course serves

The capability ladder

This course is authored to band B3.

Every course we run is written to one rung of the CASI ladder, so a plan can be assembled to take a team from where they are to where they need to be.

What do B1–B6 mean?The CASI Capability Ladder — click to expand

Every course targets a band on the CASI Capability Ladder — our six-band proficiency scale, anchored to open standards (O*NET, ESCO, NICE, NIST AI RMF, Bloom's). A band tells you how deep a course goes, and what evidence proves it.

What the learner can doTypical evidence
B1
AwareUnderstands concepts and vocabulary; uses tools with guidance
Knowledge checks
B2
FoundationPerforms standard tasks correctly in familiar contexts
Guided labs, autograded exercises
B3
PractitionerDelivers complete pieces of work independently
Scenario labs, proctored hands-on exams
B4
ProfessionalHandles production-grade complexity, trade-offs and failure modes
Break-fix drills, design defenses
B5
AdvancedEngineers systems end-to-end under constraints; leads others
Rubric-scored capstones, vivas
B6
ExpertSets direction; recognised authority across teams
Portfolio + panel evaluation

A note on B6. Courses in this catalog target B1–B5. B6 is not taught — it is recognised, through a portfolio and a panel, once someone is setting direction for others. Every journey here is built to land a learner at B5.

Next step

Run CL-322 for your team.

This course runs at several lengths depending on how deep you need to go and how much of it your people already have. Tell us who is being trained and we will scope it.

Add it to a training plan Talk to our team Check your team’s level free