4 ms·
Both can be used as a swarm of workers, that's basically what "functions as a service" are. The difference is usually in the pricing strategy. with "FAAS", yo
by camus2 10y ago
Both can be used as a swarm of workers, that's basically what "functions as a service" are.
The difference is usually in the pricing strategy. with "FAAS", you pay only when the worker works, you're not paying when the server running them is idle, as opposed to classic server instances.
App Engine standard has a few nice ideas in the way it implements push and pull worker queues, but given its limitations it was never going to be a huge success.
But "FAAS" is obviously not suitable to serve a "user facing" website, and rely heavily on vendor locked in API that cannot be transferred to another vendor.
Containerized worker jobs make more sense than "FAAS" IMHO. SAAS like iron.io provide that.
- katowulf 10y agoI'd argue there's a maintenance cost to consider as well. Functions are "serverless" from the dev point of view, where the dev needs to maintain App Engine services, scaling strategies, and so on. It's basically the next step up in the abstraction chain: On prem (you build) > Compute > App Engine > Functions.