Even so, querying data once and reusing it is usually the more maintainable option and probably means less code, too. It is not only about performance.
(And just to be clear, for my use cases, I have been very happy with SQLite's performance.)
This requires an information architecture and these days those seem to be harder to come by. I think we may be favoring velocity over Stop and Think time a bit too much.
(If you’re thinking, “no dummy, just use caching” then I regret to inform you that cache invalidation and eviction without an info architecture are as hard if not harder. And caching bugs make you look like a clown in front of your bosses. Because the whack-a-mole process never looks professional)
(And just to be clear, for my use cases, I have been very happy with SQLite's performance.)