@furystack/repository — the Repository pattern with DataSets, authorization, and event callbacks
Polling is dead, long live push. FuryStack's entity sync system gives you real-time, server-pushed updates over WebSocket — with delta replay, reference counting, auto-reconnect, and a state machine that actually makes sense.
Using extension methods was fun at the beginning but I've ran into more and more problems with them
A Repository is the next layer above the data stores. When setting up a repository, you can create DataSets that can rely on a previously configured physical store. The difference is that while PhysicalStore focuses on the data, DataSet focuses on business logic. You can authorize, check permissions, subscribe to entity changes, etc...