hermes - 💡(How to fix) Fix perf(server): implement caching for cinema schedules [1 participants]

TL;DR

Implement a caching layer using Redis to store cinema showtimes for a short period to reduce database load and response latency.

Guidance

• Review the getCinemaShowtimes function in cinema-service.ts to determine the best approach for integrating Redis caching.
• Consider using a cache key that includes the cinema ID and week start date to ensure cache invalidation when schedules change.
• Evaluate the optimal cache expiration time (e.g., 15-60 minutes) based on the frequency of cinema schedule updates.
• Update the cinemas.ts route to utilize the cached showtimes instead of fetching from the database on every request.

Example

// Example cache implementation using Redis
import { RedisClient } from 'redis';
const redisClient = new RedisClient();

const cacheKey = `cinema-showtimes-${cinemaId}-${weekStartDate}`;
const cacheExpiration = 3600; // 1 hour

const getCinemaShowtimes = async (cinemaId: string, weekStartDate: string) => {
  const cachedShowtimes = await redisClient.get(cacheKey);
  if (cachedShowtimes) {
    return JSON.parse(cachedShowtimes);
  }

  const showtimes = await fetchShowtimesFromDatabase(cinemaId, weekStartDate);
  await redisClient.set(cacheKey, JSON.stringify(showtimes), 'EX', cacheExpiration);
  return showtimes;
};

Notes

The provided example is a basic illustration of caching with Redis and may require modifications to fit the specific project requirements.

Recommendation

Apply workaround: Implement a caching layer using Redis to reduce database load and response latency, as it is a targeted solution to the identified problem.