On: Show HN: Servers.lol – Should Your EC2 Be a Lambda...

[oconnore]

I upload my code to AWS, and it gets run.

You save your code to your Intel laptop, and it gets run.

Neither of us have the complete source code that is used to run that code. You have to be ok with that, and drawing a line in the sand at the hypervisor level just seems super arbitrary.

[hueving → oconnore]

When you write against lambda and S3 it's not the same as code just being run on a laptop.

[javajosh → oconnore]

i can buy an amd laptop and run my code. where you gonna run your aws architected code if aws changes their policies to something you don't like? hint: it's called vendor lock-in.

[oconnore → javajosh]

Ok, so then I spend 5 minutes changing some boilerplate and upload it to Azure/Google Cloud/a server I bought on craigslist? Even if that did happen, I probably would still have saved time overall, because I didn't have to maintain physical infrastructure between now and whenever that distasteful policy change takes place.

[javajosh → oconnore]

nope. if your code takes 5 minutes to rewrite, then who cares? if it takes longer, then you have a big, expensive, risky problem.

[PetahNZ → javajosh]

Its not the code that take 5 minutes to rewrite, its the AWS entry point.

[javajosh → PetahNZ]

I call bullshit. But if you want to do the experiment, on video, I'll watch it.

[xienze → javajosh]

So you write to an abstraction layer rather than directly to vendor APIs.