Not sure if it counts as a pragmatic use-case, but here's my example. I recently built a little webapp [1] to send email reminders about repositories that you'

Not sure if it counts as a pragmatic use-case, but here's my example. I recently built a little webapp [1] to send email reminders about repositories that you've starred on GitHub. The motivation for it being that I have hundreds of starred repos on GitHub and can't remember what most of them are. Anyway, there is one thing I need to store in that database, users. Nothing else needs to be saved. You can accurately characterise it is a toy application that I built for fun rather than profit. But there are lots of those around and Mongo is often a good fit. If I don't need complex schemata or a huge dataset, why would I choose something else that is less easy to manage? [1] https://githubreminder.org/ https://githubreminder.org/