Menu

1 / 2

Day 12: Cross-Node Invalidation for Definition and Data Caches

DEV Community: dotnet·Jeff Tsai·14 days ago
#UmHmWxo7
#devtodotnet#devto#dev#cache#time
Reading 0:00
15s threshold

Opening one form means the framework reads more than one definition: FormSchema , TableSchema , FormLayout , ProgramSettings and LanguageResource , none of them optional. These definitions still change after go live, but they change rarely while the system is running, and data like that is the best fit for a cache. Everything left is the cache's own problem: which data fits, how finely to slice it, how long to keep it, when to release it, and how to swap in a new copy once the source has been edited.

This post covers four things, of which the notification mechanism mentioned in Why ERP Needs a Definition-Driven Framework is the third:

What goes into the cache, and in what unit

How a cache knows its source has changed

What the notification table looks like, and who writes that row

Deciding that something really changed means looking at the version, not the time

The first decides whether the cache is worth it. The other three decide whether it quietly gives out wrong answers.

1.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.