Tell me more ×  We're designing a data service that will store a
large number of statistics about stocks, including historical
data. The client will be a web application, which will need to
pull various bits of data to show in different places on the
site.  Since the different places need to show different sets of
statistics, it's not sensible for the service to simply offer
one method which retrieves all the data that we have. Since
there are so many different types of statistics, the service
isn't aware of the type of each one and simply stores them by
key.  We previously tried to deal with this by having a number
of methods which would return data objects with varying levels
of detail, for example getBasicStockInfo, getStockInfo,
getFeaturedStockInfo, getStockDetails. The trouble I found with
this was that it became tedious to add new items of data to the
objects (need to change server code), and each one would get
bloated over time as fields are added for some specific
locations on the front end. On the o