2 ms·
> Serverless, but not portable > you’ll spend most of your time figuring out how to mate these functions with other services from that cloud provider That's j
by yencabulator 5y ago
> Serverless, but not portable
> you’ll spend most of your time figuring out how to mate these functions with other services from that cloud provider
That's just as true if you move the code from serverless to a VM in that cloud, and keep using all the other services.
Vendor lock-in for the serverless function itself seems to mostly be an AWS thing (Lamdba). Elsewhere, the trend is more running any old container will function as serverless.
If you choose to consume dozens of proprietary services from a regular container, that is on you.
- throwaway2016a 5y agoAWS Lambda also supports running containers. And it supports a number of language runtimes. Including custom runtimes. The only think proprietary it imposes is the interface your function reads in when it is called. I'm curious what part of Lambda makes it have excessive lock-in vs the others once you discount "choosing to consume dozens of proprietary services"? All my serverless code always has a wrapper function to decide the request object so porting it to another cloud provider (even from Lambda) is pretty easy. Edit: The article seems to state the issue is that things like step functions are proprietary but: a. That's not lambda b. Don't use step functions, no one is forcing you. There is nothing step functions does that can't he handled other ways.
- yencabulator 5y agoLet me put it this way: AWS Lambda started out as requiring custom code, and has slowly become usable without vendor lock-in. Other providers started out with "just serve HTTP from a container".