21–30 of 31 posts
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?
A single dedicated server is not that big of an expense either. The site probably could even run on a single high end server as it is now? I guess I wouldn't have considered using something like Sheets given that. Neat idea though.
> 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
> 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.
Hi! Can you please link me to the minimum requirements for publishing blog posts on the internet? Much appreciated, thanks!
> 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.
> Certainly not really blog post material. Hi! Can you please link me to the minimum requirements for publishing blog posts on the internet? Much appreciated, thanks!
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.
It might seem absurd there is no option to pay a bunch of money for “more”, but we also don’t really know what guaranteeing that more work cost. Could be quite a bit of the sheets infrastructure is built expecting those limitations?
> 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 can get a lot of mileage out of essentially any backend technology running on recent-ish hardware, provided the devs know what they're doing.
> Our backend today is more sophisticated but our philosophy to scaling is simple, avoiding premature optimization.
> 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.