V14: Cache user by id

[Zeegaan]

Notes

• We need to cache user by id aswell, because all content have creatorId (as int) and thus when we index content, user by id gets called for each content item, therefore we need to cache the user to avoid a lot of db calls.

How to test

• Put a breakpoint in the UserRepository.Get(int id) method
• Assert that first time a user gets retrieved, the GetCacheItem should return null (not in the cache
• Assert that the second time the user gets retrieved GetCacheItem should now have a user.
• Update the users name (or something else, name is easiest)
• Get the user again, and assert that the GetCacheItem returns null (Updated user should NOT be in the cache)
• Get the user once last time, and assert that it is indeed cached again, with the updated name

[Nuklon]

This creates a lot of bulk, can also be a class.

[Zeegaan]

This is the general pattern used for these JsonPayloads, see ContentCacheRefresher & MemberCacheRefresher 😁

And IMO records are the correct type here (also the plan to change the others) as this is used purely to pass data 😊

[Nuklon]

The compiler creates a lot of unnecessary code for records, these simple types are better suited for a regular class.