Is the Google Sheets API rate limit open enough for actual production use?
I thought it was pretty restrictive, no more than 60 writes per minute, but I'm not sure about the reads restrictions.
I thought it was pretty restrictive, no more than 60 writes per minute, but I'm not sure about the reads restrictions.
This manifested as an issue when doing a deploy but being unable to get critical data. We added retries and stuff like that but it seemed not great to run a business of something that isn’t designed for this purpose.
I'm convinced most of the people in this thread haven't tried working much with Google Sheets API at scale. Most of the time it's fine, then it will have days where 30-40% of the calls (as measured by Google Cloud console API monitoring) will throw an internal error which Google advises the option for is to "try again later". Also API calls that take up to 4 minutes (?!) to return (again as measured by their own API monitoring tools in Cloud console).
It's too bad because I otherwise really like this approach.
Another problem I had is an API change one year in.
I would not use Google Sheets again. Maybe I’d try Airtable, Notion, or some other similar platform where the API access is more of a priority to the company.
My Google API rate limit is way bigger then 60/minute.
Not that hard. Like 10 lines of code to get a decentish cache going.
They're internal tools, but big ones. And I'm surprised too. You won't hit too much resistance doing things the well-supported ways, but for some reason there's no well-supported way to run a cache.