Caching
Caching reuses stored data or results. Validity and the permitted user scope belong in the design.
Caching means storing previously obtained data or results and reusing them for suitable later requests. This can avoid repeated work. A cache might sit inside an application or in front of a service.
An overview example
A hypothetical portal calculates an order overview and keeps the result for repeat requests. It does not necessarily read and calculate everything anew each time. If orders change, however, the stored overview can become outdated.
The design must determine how long a result can be used and when it is refreshed. Customer and user boundaries also apply to stored results. A fast cache hit proves neither current data nor permission to disclose it to the requesting person.
Sources
Related terms
- Cache invalidationCache invalidation ends reuse of a stored copy under defined rules. The source record remains a separate concern.
- Browser cacheThe browser cache stores suitable HTTP responses for later use. Reuse and revalidation follow the applicable rules.
- Response timeResponse time needs a defined start and end. Fetching an API response and reaching a usable view measure different sections.
- Legacy systemAn existing system still in use, with technical and business dependencies accumulated over time.
- Multi-tenancyMulti-tenancy supports separate customer or group scopes in one solution. A tenant is not automatically one person or one database.
- ThroughputThroughput describes work processed per period. It is neither the duration of one request nor the number of concurrent users.
Articles on this topic
Software Development with ASES
Custom software, web and mobile apps