Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

To you. But the world has moved on from Apple 2e and now managed hosting is analogous to serverless.

See because only science has a concrete fixed point for measuring which is the speed of light.

Human culture is subjective buzzwords where the only relative fixed point is when they learned a term.

Serverless is “managed hosting 3.0”.

First there was bare metal, run your cage. Then ec2/traditional VMs. Now just an ephemeral thread.

Computer people need to stop thinking in terms used by product & marketing people. Reasoning around it from the perspective of how it’s implemented specifically helps with the understanding.

It’s a Linux OS wrapped in layers of UX to facilitate composition of services. Unix command line tools at scale.

Cloud provider is just an OS at scale. They handle CPU, memory, scheduling, etc., all the same things a desktop OS does from the end user perspective, using a different process model we don’t generally care about as end users

Hopefully OpenAPI will help normalize this interface. Who knows though. Rich people like to drag their feet when they think sticking with the status quo gives them an advantage. Bezos may feel like making it easy to copy paste away from his cloud is a shitty idea



I can’t tell what your point is. I’m agreeing that managed hosting is the next evolution.

But Lambda is more than just for APIs. But if you’re worried about the “lock in” boogeyman for APIs, there are small packages for every language that lambda supports that allows you to run your standard Node/Express, C#/WebAPI, Python/Django/Flask API, etc on lambda just by changing the entry point.

Right now I’m deploying a Node/Express app to both lambda and Fargate (Serverless Docker) withoit any code changes.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: