Some people might consider this a newbie project to take, but yes, my company has approved (and funding) this and this one is going to be an enterprise scaled project.We are a very big eCommerce platform that can create eCommerce website that are very customizable and fully functional in less than a minute. We've been testing our digital-goods functionality with some downloadable files and it works like a charm. We want to take that to different level, by creating a buyer-supplier website which can deal in goods listed at Steam Market (which have a monetary value associated with them).The idea is to pull the details of items listed at this market and integrate that with the existing functionality of our application. I've been able to pull the data from steam and convert it into models that our application can understand (like ItemCode, ItemId, facets, etc).Now I am having trouble maintaining the schema, as I need to keep prices at my end up-to-date with the steam market. I've been using the Quartz API to create a cron-job that executes every 30 minutes and refreshes the prices. The only complexity is that steam restricts API calls to 100,000 per day (roughly 20 calls per 5 minutes).I am currently saving the market prices in MySQL database and using SpringFramework2.5 (The deprecated one) for the application.What would be a good schema design to store these prices here, as this would be a large application and Steam itself has tons of items whose details needs to be updated in my database. What techniques I can use to call the Steam API exactly 20 times in 5 minutes and still refresh all of the details?
Most optimized way of keeping market details
design patterns;schema