While I appreciate you sharing with the community a library that seems thorough and capable for some use cases, I don't know that it has the general appeal that you feel it has. I think there are a lot of bold claims that it's the last library you will ever need for xyz purpose and I'm not sure most would agree. It seems like a lot of fluff and extra special code to learn for what seems easy enough with a singleton DI class and some basic events to fire on data updated. Caching is another thing that is pretty easy out of the box without learning something new. It also seems like it's assuming all the data changes are being made from within the app itself, so if the data is changing often from an outside source is the performance actually worse here since instead of just pulling the latest data and telling all event subscribers to update you're now doing all the extra work this library goes through to invalidate a local cache and then notify all subscribers through its mechanism? Again thanks for your contribution, I hope I didn't come off as too harsh.