I want to feed an HTML5 data grid with large data sets that the client will want to manipulate in different ways, e.g. aggregation, grouping, pivoting.
The data comes from different web services and the client will be carrying out transactional operations on it.
The data grid will contain various controls for manipulating the data and will fire off requests to the server for many of them when it can't do it itself.
I envisage some sort of flattened data structure cached in the MVC layer which maintains different views on the same data. It would feed out the requested data through a pagination control to the data grid.
Presumably this has been done before in many places. Is there a design pattern to follow? Is there an open-source implementation?
1 Answer 1
I prefer using Repository Design pattern with large application, you can create repo classes that responsible for fetch data from Web Services and cached it with anyway you prefer.
I prefer using abstract Factory For Web Services and its configuration Classes which will give me extensibility to switch to new service or upgrade configurations.
also i will implement all my repos, services and configurations classes with Interfaces and inject them with IoC pattern in my web application.
Explore related questions
See similar questions with these tags.
icanhazpatternz
question, and they reached into their Gang of Four book to answer it. For what it's worth, 3rd party companies like Telerik have built grids just like this. It's a non-trivial task to do well.