This, and, in shared hosting you're paying for an instance and if you overload your traffic or utilization you're done. In 'serverless' (awful, awful marketing

This, and, in shared hosting you're paying for an instance and if you overload your traffic or utilization you're done. In 'serverless' (awful, awful marketing name for function-calls-as-a-service), your computation will be executed on one among a pool of executor units from which you are abstracted away from; therefore in theory your throughput scales to accommodate demand (impacts on your wallet notwithstanding). But this is there the name comes from -- there's no 'server' as in, a box you can ssh or sftp into and muck around with files or configurations.