3 ms·
> I do not see how a caching at ORM level could give any benefit. I don't know anything about the Python libraries as such but if they implement pluggable modu
by zimpenfish 9y ago
> I do not see how a caching at ORM level could give any benefit.
I don't know anything about the Python libraries as such but if they implement pluggable modules like memcache, redis, SysV SHM, etc., for the caching, then you can chop and change as required without having to make any application level changes[1]. Which is also handy for testing because you can supply your own mock cache module to do ... whatever.
[1] A good example would be going from "direct DB access" to "global memcache" to "local memcache backed by global memcache" - all without application changes.
- mfontani 9y ago> A good example would be going from "direct DB access" to "global memcache" to "local memcache backed by global memcache" - all without application changes. I strongly disagree: I'd rather debug something wrong with the lone application level change which added the cache support at the application level, rather than have to enter the long and deep rabbit hole of the path the code takes at the point I ask for a resultset and I get something from the DB-backed ORM, or from a global memcache, or blah. But then again, I happily develop on mostly-Perl codebase(s) ;)