Faster actions and page loads after idle
A big chunk of the app's backend was reorganized to reduce cold starts, especially on the first action after the site has been quiet for a while.
- Less waiting on common actions: Things like adding books, liking, commenting, editing, and profile updates should feel much more responsive instead of occasionally acting like the site is stuck waking up.
- Faster high-traffic reads: Shelf, profile, and discovery data now share warmer backend paths too, so common reads should load more consistently.
- Lower overhead behind the scenes: This change also reduces the number of separately warmed functions we need to keep alive, which makes the performance setup simpler and more efficient.