It's interesting and hard to justify when its economically cheaper for large corporations to crank out multiple replicas on a 'cloud' based server solutions, however thankfully the worlds moving towards a more 'serverless' approach running programs only when required instead of leaving machines on 24/7 to performer operations once an hour or so!
But the main driver behind „serverless” is not energy savings it’s again development speed and less working on ops. Serverless may have CO2 savings but this is only a side effect. Or am I wrong?
It's interesting and hard to justify when its economically cheaper for large corporations to crank out multiple replicas on a 'cloud' based server solutions, however thankfully the worlds moving towards a more 'serverless' approach running programs only when required instead of leaving machines on 24/7 to performer operations once an hour or so!
But the main driver behind „serverless” is not energy savings it’s again development speed and less working on ops. Serverless may have CO2 savings but this is only a side effect. Or am I wrong?
Oh for sure its definitely a side effect of a cost-saving measure, but its still a net positive for the environment!