Well, I wasn't talking about DB, more about memorization, but memoization which aware of its underline memoization and it will recalculate only changed parts not everything.
Imagine compilation pipeline, for example, static website generator (like Gatsby), it needs to collect dependency graph, compile JS, minimize JS, minimize CSS, generate HTML, generate unique file names, compress images, generate data files. Now you need to change only one file, do you really need to start from scratch? It depends if you change one exact page than you need to recompile only this page, if you change website navigation you will need to recompile all pages etc. The idea is that in skip this kind of task is natural you don't need to write memoization/cache invalidation for it (At least this is how I understood it, watch video author explains it better than me)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Well, I wasn't talking about DB, more about memorization, but memoization which aware of its underline memoization and it will recalculate only changed parts not everything.
Imagine compilation pipeline, for example, static website generator (like Gatsby), it needs to collect dependency graph, compile JS, minimize JS, minimize CSS, generate HTML, generate unique file names, compress images, generate data files. Now you need to change only one file, do you really need to start from scratch? It depends if you change one exact page than you need to recompile only this page, if you change website navigation you will need to recompile all pages etc. The idea is that in skip this kind of task is natural you don't need to write memoization/cache invalidation for it (At least this is how I understood it, watch video author explains it better than me)