Exercise 1: Why Fan Out One Request Per Ingredient — Possible Solution
====================================================================

THE SPECIFIC API LIMITATION
------------------------------
TheMealDB's filter-by-ingredient endpoint (filter.php?i={ingredient}) only accepts and searches against a single ingredient per request. There is no way to pass a combined list of ingredients and get back recipes matching any of them in one call - the free tier simply doesn't offer that kind of query.

WHY THIS REQUIRES FANNING OUT MULTIPLE REQUESTS
------------------------------
Since the app needs to find recipes across potentially several different expiring ingredients at once, and the API can only search one ingredient per request, the only way to cover all of them is to make one separate request per ingredient, then combine whatever comes back from each individual call afterward. There's no single-request alternative available given how the API itself is designed.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly identifies TheMealDB's one-ingredient-per-request constraint as the specific limitation, and correctly explains that fanning out multiple parallel requests is the only way to search across several ingredients given that constraint, rather than treating the fan-out as an arbitrary design choice.