salvo-caching

To reduce database load and speed up Salvo API response times, apply caching strategies like in-memory caching for frequently accessed routes. This lowers latency by serving cached data directly instead of querying the database on every request.

ETag validation optimizes client-side caching by allowing conditional requests. The API returns an ETag header, and clients send it back; if the cached resource matches, the server returns a lightweight unchanged response, saving bandwidth and processing time.

The best cache invalidation patterns for data consistency use invalidation hooks triggered when underlying data changes. This ensures cached responses are cleared or updated across microservices, preventing stale data from being served to clients.

Yes, you can integrate external in-memory stores like moka with Salvo. Optional integration with these stores supports consistent cache behavior across distributed microservices, requiring in-code TTL configuration to manage cache expiration.

You should not use in-memory caching for API routes with highly dynamic, frequently changing data or low read volumes. Caching such endpoints adds unnecessary overhead and complexity, risking stale data without meaningfully reducing latency or database load.