❔ How to prevent hardcoding a cache key when looking it up in a way that isn't hacky?
I currently have an interface which my cache-able DB entities can implement to a) mark them as able to be cached, and b) define how the cache key is formatted:
example:
Elsewhere, I define convenience methods for obtaining one of these types via a GetOrCreate:
The thing I don't like about this, however, is the fact that the
Some things I've considered:
- Instead of hardcoding the ID in my GetOrCreate (or GetOrFetch) methods, I could
.
- Using reflection in some yet-to-be-thought-of way to accomplish this programmatically. But that seems like it would have a more than negligible performance hit across hundreds or thousands of read calls here.
example:
Elsewhere, I define convenience methods for obtaining one of these types via a GetOrCreate:
The thing I don't like about this, however, is the fact that the
ICachedDbEntitySome things I've considered:
- Instead of hardcoding the ID in my GetOrCreate (or GetOrFetch) methods, I could
new().CacheKey- Using reflection in some yet-to-be-thought-of way to accomplish this programmatically. But that seems like it would have a more than negligible performance hit across hundreds or thousands of read calls here.
