Hacker News Reader

From what I've seen with serverless, it doesn't look that hard to build your own runtime for it if you did want to run outside of your vendor and avoid lock-in. It would turn your stuff back into a stack of containers, of course.

View on HN

That’s the relatively easy part. There’s also a lock-in with all the integrations as you probably need to have some sort of persistent storage and all the other managed services helping to cope with the complete statelessness.

And you have this with containers as with serverless. So no argument here.

No, with Kubernetes, you specify, for example, that your app needs block store of a certain size or ingress at a certain port. The runtime knows how to satisfy that on each cloud.

What I meant was, when you set up the container and got your data in S3, it is in there, same goes with serverless.

Nobody prevents you to write your serverless function so it needs a block store of a certain size or ingress at a certain port.

But there is no standard way to specify those requirements in a cloud agnostic manner.

Reply on news.ycombinator.com