4 ms·
Is lock-in that big of a concern for people who are using serverless? I have no direct experience here, but my understanding was that all the major serverless p
by mumblemumble 6y ago
Is lock-in that big of a concern for people who are using serverless? I have no direct experience here, but my understanding was that all the major serverless platforms are built on proprietary APIs.
That said, this item from the FAQ is nice to see; I'd love to see more vendors not just making promises along these lines, but making them binding:
> if the worst should happen, we will open-source Dark ... We're committed to codifying the specifics in a legal framework
- imglorp 6y agoYeah lockin is a problem in general for serverless if you need all the cloud vendor's extras. For example, lambda doesn't make sense without IAM, VPC, etc and you often want things to hook to it like SQS, API Gateway, database, cognito, etc. Instead of lockin, you can run serverless in your own framework though, such as Kubeless or Knative, which could be deployed on prem or in a more generic cloud deployment.
- yellowapple 6y agoDoesn't that kind of defeat the point of "serverless", though? I mean, I guess if that's how you like to structure your code then go for it, but the primary marketing pitch I've ever heard was around it, you know, absolving developers of the need to worry about servers. I guess if you've got a large enough environment that you have dedicated devs pushing things to Kubeless/Knative instances maintained by dedicated ops/sysdmins, then maybe that's the niche there?
- jacques_chester 6y agoIt depends on what you think "serverless" means. Is it solely about the developer experience? Or is it about the economic ownership of hardware? Or both?
- imglorp 6y agoI was referring specifically to lambda-style "functions as a managed service", which might be a better term than serverless. Managed instance would be serverless by the economic definition.