11–20 of 31 posts
As a side note: it's nearly impossible to upgrade to a higher Sheets API rate limit. We tried it all: options in Cloud Console, speaking with support, talking to sales reps. Google simply doesn't want that money and doesn't care if you are hitting limits and want to upgrade.
This seems like 5 years down the road this is going to turn into a horror story on HN, about "I went to this customer, and they had been running their entire company database on a single Google Sheet, and now are panicking because the secretary accidentally just deleted everyone from pay roll."
> Even now, one of our most trafficked services today still has a single node.js instance serving 60K requests per hour (topic for another blog post). So 60k per hour is 1k per minute is 16 per second. That is... not that much? Certainly not really blog post material.
EDIT: s/of/off/
> Even now, one of our most trafficked services today still has a single node.js instance serving 60K requests per hour (topic for another blog post). So 60k per hour is 1k per minute is 16 per second. That is... not that much? Certainly not really blog post material.
You could serve that with a shell script running off an uncached floppy. EDIT: s/of/off/
So when they say they're running without a server it means they are running on Google servers? I thought serverless meant.. no servers
So when they say they're running without a server it means they are running on Google servers? I thought serverless meant.. no servers
This seems like 5 years down the road this is going to turn into a horror story on HN, about "I went to this customer, and they had been running their entire company database on a single Google Sheet, and now are panicking because the secretary accidentally just deleted everyone from pay roll."
I'm not sure if I'm saying this seriously or not, but: no worries! In addition to its granular permissions systems which will now let you revoke the secretary's access, Sheets also has a robust backup and restore story built-in! Just click File -> Version history and rollback the offending change. (You can do a live preview of what the effect will be, to confirm you're rolling back the right change.) The problem Shee…
It's a horror show that you can run a major bank on it... but also not, because you can run it pretty well.
I guess I'm confused, if you're already running Cloudfront, API Gateway, and lambdas, why you'd bother to make API calls out to Sheets rather than just plunking down a simple DynamoDB? Maybe the data access patterns are more complicated than I'm thinking, or just to capture the built in Forms -> Sheets data entry flow?
Sheets gives us an admin tool, BI tool, Charting, 'ETL', simple schema changes, etc. all-in-one.
Note we actually still use Google Sheets for some things like storing the list of companies. Just today, I needed a quick way to summarize the description of each company into a few words. I installed an add-on for =GPT() formula. Within a few minutes I had done ETL, column addition, made API calls, etc. 0 code.