4 ms·
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
by brutopia 9y ago
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.
- k__ 9y agoAnd you have this with containers as with serverless. So no argument here.
- ec109685 9y agoNo, 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.
- k__ 9y agoWhat 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.
- ec109685 9y agoBut there is no standard way to specify those requirements in a cloud agnostic manner.