Ideally on Serverless infrastructure the system would
"move" jobs around so they run on the optimal platform
for what they are doing continuously?
(Based on price or based on raw compute etc)
I know there are many reasons this will be difficult in
real life, but it sounds like where it should be heading.
> Ideally on Serverless infrastructure the system would "move" jobs around so they run on the optimal platform for what they are doing continuously? (Based on price or based on raw compute etc)
AWS Lambda supports about half a dozen runtimes, some based on interpreted languages, and some based on compiled languages. Thus you can't simply move golang or rust code between completely different architectures and expect things to work.
Also, one of AWS Lambda's usecases is having your runtime call precompiled binaries. I'd be pissed if my Lambda's ceased to work because AWS decided to run my trusty python-calling-C++ lib Lambdas in ARM just because they want to push people towards graviton.
I know there are many reasons this will be difficult in real life, but it sounds like where it should be heading.