Caching

Optimized caching saves both database query time and CPU processing time on every request, compounding the performance benefit. Basic caching eliminates repeated database round-trips and reduces database load. Database-level server-side caching does not eliminate network transfer overhead because the same data is still transmitted on every request. Optimized caching stores the processed result of data in Redis, not just the raw database rows. Basic caching works by copying rows from the primary database into Redis and serving subsequent requests from Redis instead. Caching stores frequently accessed data in a fast-access location such as Redis to avoid repeated database queries. Without caching, every request for the same data triggers a new database query regardless of whether the data changed. Omitting application-level caching is one of the most reliable ways to destroy performance at scale. Redis is well-suited for caching frequently requested data to avoid hitting the primary database. Application-level caching is required to fully solve the repeated-transfer problem; database-level caching alone is insufficient.