3 ms·
The most popular use cases for serverless are gluing different services together, where critical metrics are network throughput, network latency, and CPU schedu
by arpinum 8y ago
The most popular use cases for serverless are gluing different services together, where critical metrics are network throughput, network latency, and CPU scheduler. Fibonacci is not an interesting use case on its own, nor is time-insensitive computational work in general. Sustained 100% CPU usage is not affordable on these platforms.
When used in conjunction with a database, KV store, or blob storage, total latency for the end user is dominated by the CPU scheduler for small instances, and network quality for larger instances. Except Azure of course, they are still trying to figure out how to bolt serverless onto App Services without re-engineering the stack.