Caching
Reusing work, and knowing when to stop.
3 subjects · 5 topics · 1 area
Subjects covering this category
3 subjects- Subject · Beginner to Advanced
Turning a product's requirements into a first design for a web system, and knowing what each part is there for.
- Starting a Design
- The Parts of a System
- Moving Data Around
- Subject · Intermediate to Advanced
Building a REST service with Spring Boot: wired to real data, validated, and fast enough to trust in production.
- Spring Boot Essentials
- Building REST APIs
- Data Access
- Subject · Beginner to Advanced
Designing HTTP APIs that clients can understand, call safely, and keep using as the API changes.
- HTTP for API Designers
- Designing the Contract
- Repeats, Retries and Long Jobs
Redis
1 topic- System Design
Caching: keeping copies of frequent reads close, deciding when they go stale, and the ways a cache can take a system down.
Beginner to Advanced9 cards · 8 qnot started
In Caching itself
4 topics- API Design
HTTP caching for APIs: telling clients and CDNs how long to keep a response, and using ETags to skip unchanged downloads and to stop two clients overwriting each other.
Beginner to Advanced11 cards · 8 qnot started
- Spring Boot
Caching in Spring Boot: @Cacheable, @CachePut and @CacheEvict, cache keys, caching strategies, and the default provider's limit.
Intermediate to Advanced7 cards · 5 qnot started
- System Design
System design heuristics: matching a pressure such as read-heavy traffic or global users to the pattern that answers it.
Intermediate to Advanced7 cards · 5 qnot started
- System Design
Load balancers, reverse proxies and API gateways: the three kinds of server that sit in front of yours, and the one job each is for.
Beginner to Intermediate10 cards · 5 qnot started