4 ms·
Can you clarify this point: > its strength is in distributed processing; in other words, long-running CPU-bound apps. it seems to me that's an explicit non-us
by gallamine 9y ago
Can you clarify this point:
> its strength is in distributed processing; in other words, long-running CPU-bound apps.
it seems to me that's an explicit non-usecase for Lambda given it limits sessions to < 5min per invocation.
- scrollaway 9y agoI should have been more specific yes. I actually meant CPU-or-network-bound tasks with a predictable, sub-5min runtime. Like I said we use it for game replay processing, so that's 5-15 second tasks that read and parse log files and hit a db and s3 with the results. Other suitable tasks: image resizing, API chatter, bounded video transcoding, etc. Lambda is pretty good at distributed processing (as long as you can make the bill work in your favour, over hosting your own overprovisioned fleet).