> I'm not sure how you would split out these network vs compute items without > action devs taking that responsibility (and not using libraries) or how it > would be done generically across runtimes.
You don't think this is already happening? When you use promises and chain promises together, you've already decomposed your computation into smaller operations. It is precisely this that makes the asynchronous model of computing work - even in a single threaded runtime. I think this can be exploited for a serverless polyglot composition. That in itself is a separate topic from the one your raised initially. I think the opportunities for packing computation at finer granularity will be there. In your approach you're tending, it seems, toward taking monolithic codes and overlapping their computation. I tend to think this will work better with another approach. In either case, figuring out how to manage several granularities of concurrent activations applies. -r
