Exercise 3: Two Different SQLite Concerns, and Why Each Course Names a Different One — Possible Solution
====================================================================

THIS COURSE'S CONCERN: EPHEMERAL STORAGE
------------------------------
Because the entire database lives in one file on disk, this course's concern is about the deployment platform's own filesystem behavior - if that platform wipes local storage on every redeploy or restart (an "ephemeral filesystem," common on many simple hosting platforms), the database file itself would be deleted along with everything in it, regardless of how many or how few users are actually using the app at once.

FOOD TRACKER (DJANGO)'S CONCERN: CONCURRENCY
------------------------------
Django's own deployment chapter instead named SQLite's file-level locking as the relevant risk - a genuine bottleneck specifically under real multi-user, high-write-volume load, where multiple simultaneous writes have to wait on each other because SQLite locks the whole file rather than individual rows.

WHY EACH COURSE NAMES A DIFFERENT ONE AS MORE RELEVANT
------------------------------
Both risks are real properties of SQLite in general, but which one is the more pressing concern depends on the specific deployment context each course is actually describing. This course's deployment discussion centers on running the app on a typical hosting platform, where storage persistence is the more immediate, practical risk to check for before deploying at all. Concurrency was never really the risk at this app's own realistic single-household scale, where near-simultaneous writes are extremely unlikely regardless of platform - so this chapter reasonably emphasizes the storage-persistence issue as the one actually worth worrying about here.

WHY THIS WORKS AS AN ANSWER
------------------------------
It correctly identifies both concerns specifically (ephemeral storage here, concurrency in the Django course), and correctly explains that each course emphasizes the concern most relevant to its own deployment context and this app's own realistic scale, rather than one course being right and the other wrong.