obcilion

3 ms·

1.
by obcilion 5y ago
I think it's a decent architectural decision. It's a lot easier to develop solid code that handles a single request than code than handles multiple requests in parallel. Functions are used for a lot more than HTTP, we use them for
2.
by obcilion 5y ago
The NodeJS application is single-threaded, but the Node EventLoop can handle a huge amount of parallel requests, especially since most of the time per request is spent waiting for calls to the DB or external APIs. I believe the majority of
3.
by obcilion 5y ago
Thank you for letting us know! We set our front-end guy on it and it should be a lot better now.
4.
by obcilion 5y ago
It's REST but we don't do HATEOAS. All indicators points to it being a lot of work with little to no reward.
5.
by obcilion 5y ago
I believe the team responsible for functions, both for GCP, AWS and Azure, do great work in optimizing functions, far, far better work than we could have done on our own. The problem in our case is that they are architectured to only suppor
6.
by obcilion 5y ago
The Firebase suite has been _fantastic_ for developing our app, to quote one of the app developers: "[...] but from start until now, I feel we have saved years of shitty bugs, and that it is one of the best decisions we have done"
7.
by obcilion 5y ago
It is a full-fledged REST API, but we don't do a lot of caching (other than through Cloudlfare) as most of our endpoints either have volatile data or do various operations.
8.
by obcilion 5y ago
I agree! We initially measured in percentiles, but during an internal presentation someone said it was too hard to understand and now we've lost the data :(
9.
by obcilion 5y ago
Thanks for letting me know :) Definitely not on the same IP, but I sent an email nonetheless.
10.
by obcilion 5y ago
I haven't read the entire article, but I assume you need someone to admin the cluster? How does the savings in billing compare to work needed for maintenance?
11.
by obcilion 5y ago
If cold starts wasn't a problem we probably would have stayed with functions, and all of our non-api stuff is still on functions.
12.
by obcilion 5y ago
Hi! Author here. Functions still only run a single request at a time, while Cloud Run can run as many as the container can handle. We want to build for multiple smaller requests, so when we get ~10k requests incoming in a short timespan it&