We are attempting to build an application that initially will cache data in a MYSQL sever.  This has 2 advantages:

1)  We can more easily write queries against the data as we will have tables that are supplemental to the FRC Event data
.

and

2)  It won't directly pound the FRC severs as much.  (At least that is the hope.)

Just wondering if others have done this and if there are any guidelines for setting it up. 

For example, we have a table reflecting the team data.  There are 3,144 teams.  It probably only needs to be refreshed 
once a week in the off season and maybe daily during the regular season.  

For event data, match results should potentially be refreshed once a minute while the event is going on.

The FRCEvent API does not appear to be setup to do effective caching.  For example, if we wanted to refresh only the 
teams that have updated their information in the last 2 days, instead of all 3,144, there does not appear to be a way to
 get the delta quickly.  So, we would have to refresh the full list.  There does appear to be other ways to limit the 
amount of data requested in other areas of the FRC Event API so that we are not doing a fully refresh every time.  

So we are very carefully writing the caching mechanism to have minimal overall impact.

We have already started to test a mechanism and will monitor the results closely.

I would appreciate any feedback on cacheing the data in general.