Remember this
Cache reduces repeated work. Load balancing spreads live traffic across server copies.
Use them only where your design has a reason. In your submission, say what becomes faster, what can go stale, and what happens when one server fails.
Where cache fits
A cache stores a recent answer close to your app. It is useful when many users ask for the same data, like college event listings, product catalogues, leaderboard pages, or user profiles.
Do not cache everything. Cache reads that are common, slow, and safe to be slightly old for a short time.