Qfyilyi

I am using the Google Calendar API to preprocess events that are being added (adjust their content depending on certain values they may contain). This means that theoretically I need to update any number of events at any given time, depending on how many are created.

The Google Calendar API has usage quotas, especially one stating a maximum of 500 operations per 100 seconds.

To tackle this I am using a time-based trigger (every 2 minutes) that does up to 500 operations (and only updates sync tokens when all events are processed). The downside of this approach is that I have to run a check every 2 minutes, whether or not anything has actually changed.

I would like to replace the time-based trigger with a watch. I'm not sure though if there is any way to limit the amount of watch calls so that I can ensure the 100 seconds quota is not exceeded.

My research so far shows me that it cannot be done. I'm hoping I'm wrong. Any ideas on how this can be solved?

AFAIK, that is one of the best practice suggested by Google. Using watch and push notification allows you to eliminate the extra network and compute costs involved with polling resources to determine if they have changed. Here are some tips to best manage working within the quota from this blog:

• Use push notifications instead of polling.


• If you cannot avoid polling, make sure you only poll when necessary (for example poll very seldomly at night).


• Use incremental synchronization with sync tokens for all collections instead of repeatedly retrieving all the entries.


• Increase page size to retrieve more data at once by using the maxResults parameter.


• Update events when they change, avoid re-creating all the events on every sync.


• Use exponential backoff for error retries.

Also, if you cannot avoid exceeding to your current limit. You can always request for additional quota.