4 ms·

You're right about the way language works, but how to probe the usage of a neologism like this without discussing (criticizing) the word? 'trolling' makes it s

You're right about the way language works, but how to probe the usage of a neologism like this without discussing (criticizing) the word? 'trolling' makes it sound like critics are acting in bad faith. : (

scarface74 8y ago
They are dealing in bad faith when they post the usual retort - “why is it called serverless? Don’t you idiots know there are still servers involved?” Not directed at you, just speaking hypothetically. In the context of AWS... App/web servers EC2 — I don’t have to manage the underlying hardware but I still have to either overprovision to deal with spikes, setup autoscaling based on metrics that I define, write scripts to make sure that new instances in an autoscalimg group is up to date, deal with OS patches. Serverless - lambda - I give AWS a zip file and do a little configuration. It figures out how to autoscale. Build servers Same issues as above with EC2 and my build environment has to have everything every developer needs to build and one configuration can interfere with another developers build. Serverless CodeBuild - I create a Docker image of my build environment or use one of the prebuilt ones and tell CodeBuild to spin it up on demand. If 10 developers need to build ten different repos at once, No problem. When no one is building, no charges. Databases EC2 - all of the problems about the EC2 and I have to manage OS patches, database patches, replication, and backups RDS - removes most of those issues. Serverless Aurora/DynamoDB. You don’t have to worry about “instance sizes”. Docker. ECS vs. Fargate - same as above With lambda.