Given that the client didn't want to move his server for is current hosting provider, but was complaining all the time of how slow things were, I realised that I had to find a way to improve application responsiveness by having the data already stored locally when the user/UI actually needs it.
So, devised a strategy of keeping a local cache and using web sockets to notify my local cache that local data as dirty and needs to be updated.
Conceptually, I like the idea of having my cache resembling a database and and an ORM implementation. Having that I mind, my implementation would require the following components:
* An Entity, that will map to a server side collection of data (usually a table but can actually be just a view)
* A local cache/db, that will store a set of entities and provide convenient API's to access them
Your new post is loading...