20 ms·
“Lambda and serverless is one of the worst forms of proprietary lock-in” (2017)
- reilly3000 8y agoI the Serverless framework and have been able to successfully redeploy functions from AWS to GCP (all node, this was in 2018) with only a few changes to the Provider section off serverless.yml. We are adopting Kubernetes now and I'm feeling out the landscape, so I'm planning on trying the same thing with Kubeless. AFAIK it should be pretty seemless- I'm more worried about Ingress working properly than Kubeless not being able to run my code. FaaS has an important role to play: we often prototype things with Zapier, then redeploy them as FaaS functions when we need to scale them or process any PII. I can't imagine trying to make a full app with them with the current state of the dev/testing workflow, but for internal systems, integration, and stream processing they are pretty tough to beat.
- type0 8y agofrom 2017
- dang 8y agoAdded. Thanks!
- AnimalMuppet 8y agoHow do you do that? With all the stories in play, and all the comments being added, how do you notice within four minutes that one of them says to add the date to a title?
- Robin_Message 8y agoI wonder if a regexp for a short comment containing a single date would work. I expect comments matching that regex are streaming by, Matrix style, on one of dang's many monitors¹, as he sips his morning cold-pressed flat grey². In fact, with a bit of practice, there is probably a regexp that catches all of them. ¹ I haven't seen dang's workstation, I'm just imagining. ² Sorry, doing it again.
- lucbocahut 8y agoit could simply be looking at https://news.ycombinator.com/newcomments https://news.ycombinator.com/newcomments :)
- pjc50 8y agoUndoubtedly dang has a continuous feed of incoming comments, scrolling like Twitter, each with a flag and banhammer button.
- dang 8y agoI'm afraid it's pretty random.
- Bucephalus355 8y agoThere is a certain amount of arrogance to always being afraid of vendor lock-in. Most companies don’t survive, even the best ones might be just around for 20-25 years. The big worry should be on building a business that won’t immediately die. And even with Oracle (probably the primo example of lock-in) it’s not like there aren’t firms who’s sole speciality is pumping data out of the Oracle DB and transforming it magically into T-SQL. It’s never the end of the world with vendor lock-in. NOTE: now vendor lock-out does scare me like no other ironically
- travisjungroth 8y agoBy lock-out do you mean the vendor shuts down, or you get banned, or something else?
- sattoshi 8y agoI suspect it means using technology for which a vendor drops support.
- freehunter 8y agoNot the person you're responding to, but I worry about (and have experienced) both with my tech stack, even as I've purposefully switched vendors multiple times with minimal headaches. Locking yourself into a single vendor is easier to voluntarily work your way out of than your vendor shutting down or shutting you out unexpectedly. But the good news is if you plan for one you get the other for free.
- ergothus 8y ago> It’s never the end of the world with vendor lock-in. I think that's a matter of scale. Using Oracle for your counter example isn't very persuasive, as that's a huge vendor, so there's a market to extract you. Not so for many other vendors. > Most companies don’t survive ...and ensuring they can control their costs and pivot away from solutions that prove too complex is part of being able to survive. I mean, I agree, vendor lock-in doesn't have to be the end, but it also makes sense to extricate yourself when you can. When I worked for Virginia state govt they made a deal with Northrup Grumman...one that the legislative audit group came by later and said it was such a terrible deal that we should drop it...except we couldn't afford the exit costs, so we had to stick with a deal that was bad in terms of both money and quality. That's a position you don't want to be in, and that result "It's bad but we can't afford to get out of it" is what the fear of vendor lock in is all about.
- milesward 8y agoUnless your serverless platform is OSS... https://github.com/knative/ https://github.com/knative/
- BryantD 8y agoOr https://github.com/fnproject https://github.com/fnproject . I think best practice is to think of serverless deployment as a technical operations technology, rather than as a methodology to eliminate the need for technical operations. Don't lose track of what you're effectively outsourcing to your serverless provider. Have a backup plan, just like in the old days you wanted a backup plan in case your datacenter provider had issues.
- QuinnyPig 8y ago"I'm scared of vendor lock-in, so I'm going to build something that's completely provider agnostic" means you're buying optionality, and paying for it with feature velocity. There are business reasons to go multi-cloud for a few workloads, but understand that you're going to lose time to market as a result. My best practice advice is to pick a vendor (I don't care which one) and go all-in. And you'll forgive my skepticism around "go multi-cloud!" coming from a vendor who'll have precious little to sell me if I don't.
- thekingofh 8y agoThe problem with that is, there's only one thing, some product manager somewhere, that sits on a light switch of your company or project's success or failure. They could even unintentionally end you with a price change.
- taneq 8y agoAnd we see this here regularly, as with the Google Maps API price hike.
- scarface74 8y agoNo you just see that with Google...a company not exactly known for its customer relations.
- hopler 8y agoAnd Oracle, and IBM, and every company that doesn't pour every dollar of profit into growth marketing to continue redoubling down with investor money.
- scarface74 8y agoAWS drives most of Amazon’s profits these days. It isn’t running at a loss.
- justasitsounds 8y agoA lot of embittered Ops engineers shaking their fists in the comment thread of that article. "Real engineers write assembly, on punchcards, blindfolded" etc.
- scarface74 8y agoThis is not true. For example: Using this template. https://github.com/awslabs/aws-serverless-express https://github.com/awslabs/aws-serverless-express I’ve been able to deploy the same code as a regular Node/Express app and a lambda with no code changes just by changing my CI/CD Pipeline slightly. You can do the same with any supported language. With all of the AWS services we depend on, our APIs are the easiest to transition. And despite the dreams of techies more than likely after awhile, you aren’t going to change your underlying infrastructure. You are always locked into your infrastructure choices.
- dangerboysteve 8y agoYou could always deploy your own FAAS cluster. https://www.openfaas.com/ https://www.openfaas.com/ https://openwhisk.apache.org/ https://openwhisk.apache.org/ and others.
- scarface74 8y agoAnd then I have something else to support. Kind of the whole point of using AWS not to have to support infrastructure unnecessarily. On top of that. I lose the “easy button” of depending on our AWS business support contract if something gets wonky.
- falcor84 8y agoYou don't necessarily have to host this yourself. With this, there's a relatively straightforward (but obviously not necessarily easy) way for Joe Entrepreneur to set up a hosted service to compete with AWS Lambda, thus helping the community avoid vendor lock-in.
- scarface74 8y agoSo can Joe Entrepreneur also host my databases? my storage? My CDN around the world? My ElasticSearch cluster? My Redis cluster? All of my objects? Can he provide 24 hour support? Can he duplicate my data center for my developers in India so they don’t have lag? What about my identity provider? My Active Directory? Can he do all that across multiple geographically dispersed redundant data centers?
- swamp40 8y agoThis is interesting: We've heard from our customers, if you cross $100,000 a month on AWS, they'll negotiate your bill down," said Polvi. "If you cross a million a month, they'll no longer negotiate with you because they know you're so locked that you're not going anywhere. That's the level where we're trying to provide some relief.
- bgroins 8y agoAs someone who has negotiated with AWS at the $1m/month level this is completely false.
- CodeWriter23 8y agoHow much did they move on the price?
- Someone1234 8y agoI've also negotiated with AWS, and both your position and their position strikes me as equally true. There's certain products of theirs that they just aren't going to negotiate on, because they know they've got you, whereas others the clouds part and discounts rain down. It certainly used to be this way when AWS had less competition, these days there's an Azure/Oracle Cloud/Rackspace/Google/etc alternative to most of their greatest hits, which gives a greater negotiating edge.
- redisman 8y agoLambda certainly has more alternatives than Dynamo for example. But I guess the true lock-in is the integration. If you use Lambda, chances are you'll end up choosing S3 and SQS and Dynamo and API Gateway etc.
- outworlder 8y ago"If you cross a million a month, they'll no longer negotiate with you because they know you're so locked that you're not going anywhere" If they think you are unable to move at all, that may be true. The tone changes once you realize that either you can move, or you can't, but there's a lot more business coming and they won't get it.
- kondro 8y agoUnsurprising that when your continued existence (in this case CoreOS) relies on something being true, that every alternative to that is false.
- adjkant 8y agoAfter using lambda and serverless myself over the past year, I really struggle to see where this lock-in is. If you're already writing a stateless API as most are these days, and the cloud platforms support many language options, going between say EC2 and Lambda really isn't that much difference in code. If that changeover time is too costly for you, that's far more likely a sign of changing infrastructure too often.
- robrtsql 8y agoIn my opinion, the real lock-in is not the stateless API, but the tie-ins with other AWS services that may end up being required to accomplish what you need. Like, if you're trying to provide a calculator API, you can definitely run that in Lambda and then easily move it somewhere else when AWS does something to upset you. But, let's say you're trying to do something a little more complicated (a common example is validating and transforming profile pictures for some sort of app), you might end up using AWS Step Functions and SQS. Your code is still portable but it relies on a bunch of managed services.
- dr01d 8y agoIn most cases, very few companies have products that need to scale to extreme load day 1 or even year 1. IMO, instead of reaching for the latest shiny cloud product, try building initially with traditional databases, load balancing, and caching first. You can actually go very far on unsexy old stuff. Overall, this approach will make migration easier in the cloud and you can always evolve parts of your stack based on your actual needs later. Justify switching out to proprietary products like lambdas, etc once your system actually requires it and then weigh your options carefully. Everyone jumping on the bandwagon these days needs to realize: a LOT of huge systems are still rocking PHP and MySQL and chasing new cloud products is a never ending process.
- scarface74 8y agoAnd while we spend all of our energy and money doing that, we aren’t actually creating the product that is suppose to be bringing us revenue....
- wUabkSG6L5Bfa5 8y agoThis is the correct answer. AFAIC, Intro to Economics should be the first CS course any software engineer takes.
- nickthemagicman 8y agoI have mixed feelings about this and I don't have enough experience to label on method better than the other. Lambdas basically require zero maintenance. SQS requires zero maintenance. EC2 load balancer is zero maintenance. And the setup is trivial too and there's no migration time down the line.If you start off with native cloud for everything you can keep your maintenance and setup costs down drastically. However, a lot can be done with the old school unsexy tech. So I'm mixed.
- dr01d 8y agoZero maintenance? What about standing up multiple environments for staging, prod? Sharing secrets ,keys, and env vars? Deployments? Logging? No migration time down the line? I'm pretty sure GCP, Azure don't have Lambda, SQS, or EC2 load balancers so you absolutely will have migration time if you have to retool your implementation to switch cloud providers or products.
- seniorsassycat 8y agoOf all the AWS features to criticism for lock-in, Lambda seems like the weakest choice. You don't have to write much code to implement a lambda handler's boilerplate, and that boilerplate is at the uppermost or outermost layer of your code. You could turn most libraries or applications into lambda functions by writing one class or one method. A lambda's zip distribution is not proprietary and is easy to implement in any build tool.
- Karunamon 8y agoI'd include the triggers as part of that analysis, like being able to invoke a function every time something is pushed to an S3 bucket for example. Just being able to run arbitrary functions without caring about the OS is the core product, but the true value is that you can tie that into innumerable other services that are so helpfully provided. Basically, AWS has so much damn stuff under their belt now, and it all integrates so nicely, every time they add a new feature it lifts up all the other features as a matter of course.
- sonnyblarney 8y agoAgreed. Vendor lock-in is a thing, but Lambda are lower on the rungs than other things. It's the hyper-specific things that imply heavier lock-in, especially those that bleed into other systems.
- javadocmd 8y agoI tend to agree, although with most things I think it depends on how heavily invested you are. Migrating a handful of mission-critical Lambdas is no biggie, but if you've really bought the bait and implemented your entire web services architecture on AWS API Gateway and Lambda -- for some reason -- you've got a much tougher job untangling yourself. Perhaps it suffices to say it's worth keeping an eye on how much friction you're building for yourself as you go.
- fishnchips 8y agoI’m not buying that. Lambda is merely an execution environment. In most Lambda functions I write, the Lambda-specific bit is tiny, and could be easily replaced without affecting business logic. On the other hand, most Lambdas I write interact with other AWS APIs, which is where the real lock-in is. The effort to eg. move the data off Dynamo is substantially higher than what’s required to switch that bit of code to run on k8s and consume a Kafka topic.
- TheRealPomax 8y agoCool. What part aren't you buying, the title of this post, or the actual five paragraphs in the article that actually give you the context of that title?
- CrankyBear 8y agoAh.. this is an ancient story and it's really all about promoting Kubernetes rather than dissing Lambda.
- tnolet 8y agoYes, a lock-in that can be avoided with a 20 to 30 line piece of Javascript that just handles the messages and passes it to your cloud agnostic piece of business code.
- scarface74 8y agoMore like two - deserialize event - pass object to your business logic.
- jniedrauer 8y agoI use lambda to perform simple, stateless units of work like autoscaling event post-hooks, chat bots, routine scheduled tasks, etc. They're mostly cloud-agnostic and I could move them to a server if I had to. I don't think anyone can really build a full scale application using serverless. It's just not performant or predictable enough. I've seen people try, and it always ended in frustration. A properly configured docker scheduler is better for this type of work anyway.
- sanxchit 8y agoYou can definitely build a fully functional web app using just serverless. For an example, take a look at https://acloud.guru https://acloud.guru . Where I work, we almost exclusively use serverless, and I have found it to be incredibly reliable, and way more hands-off than a docker deployment.
- shiado 8y agoSomebody should make a movement called 'serverful' that builds technologies that allow you to deploy a web service on any arbitrary server in any cloud that scales to the amount of resources the server is capable of consuming. You could just reskin Apache and call it a day.
- WrtCdEvrydy 8y agoThis is called 'Flynn' and it just works. Abstracts your database, load balancing and most functions that AWS provides. You can even add minio as an S3 compatible data storage.
- taneq 8y agoThey need a snappy new name for it, though. "Web hosting" or something.
- Aeolun 8y agoThat sounds a bit outdated. “Web-scale hosting” has that little bit of extra oomph.
- deleted 8y ago[deleted]
- altmind 8y agoThere is a great list of self-hosted services, i think the author will be happy for merge requests with more services https://github.com/Kickball/awesome-selfhosted https://github.com/Kickball/awesome-selfhosted
- simonh 8y agoIsn’t that what containers and Kubernetes are for?
- deleted 8y ago[deleted]
- nilshauk 8y agoI would argue that small to medium web services don’t need Kubernetes nor serverless. It doesn’t even need to be split into services. Build a tidy monolith and see how far that takes you first. Have less moving parts. Yes, serveless ties you in to platform specifics but in their nature the functions you create should be small and easy to reimplement elsewhere. Kubernetes on the other hand is arguably also a certain lock-in, by virtue of being complicated. No wonder vendors love it, it’s an offering that is hard to do right in-house. And when Kubernetes releases updates only the most seasoned in-house teams will be able to keep up. It creates job security by being a lot to learn and manage. Yes there are good abstractions but when something breaks you’ll need to delve into that complexity below. (Makes me think of ORM abstractions vs SQL.) Yes, Kubernetes is an awesome vehicle for orchestrating a swarm of containerized services. But when you’re not Netflix or Twitter scale it’s ridiculous to worship this complexity. Frankly I keep coming back to appreciate Heroku's abstractions and its twelve factor app philosophy https://12factor.net/ https://12factor.net/. Heroku runs on AWS but feels like a different world than AWS to develop on. I can actually get projects flying with a 2-3 person team me included.
- halbritt 8y agoThere's a world of organizations between Netflix and Twitter scale and small startups with 2-3 person infrastructure teams in which Kubernetes makes good sense. At some point, it becomes cost effective to have a two-pizza team of engineers dedicated to it. Once an org hits that level, then the scale that can be achieved with Kubernetes is pretty immense.
- allochthon 8y agoI'm using k8s for a side project on Digital Ocean. I'm familiar with k8s, and deployment and maintenance are easy. The only devops I've gotten into so far is setting up DNS for the external load balancer. I think people are mistaken when they say k8s is too complex for the smallest apps.
- sonnyblarney 8y ago" don’t need Kubernetes nor serverless." Actually 'serverless' is where small shops might want to start. A single Lambda can encompass a whole variety of functions, and if you're using a datastore that scales as well, you don't need to worry about much. Once it's set up, it should be very easy to monitor and change. I'd rather a simple Lambda than managing a couple of EC2's with failover scenarios and the front end networking pieces for that.
- jimmychangas 8y agoYeah, absolutely, if your engineers decide to adopt serverless due to hype or just to improve their own curriculum, you are going to spend a lot more on infrastructure than you would by provisioning VMs or running containers. By being selective about which workloads are eligible to become FaaS and doing a little of optimization, however, you can cut some costs and avoiding overprovisioning, with automatic and efficient scalability. I believe that, in most cases, it is better to control the exit costs of your architectural decisions than to avoid lock-in at all costs.
- Coredalae 8y agoThis is why the serverless framework (trying to give the possibility to deploy to any cloud provider) is so important. Some repetitive simple tasks are extremely well suited for lambda/functions /whatever name and some tasks are suited for big machines with gazillion terraflops and terabytes of ram. The job of the engineer is to know what his software needs, and what the most optimal path for this is. Business is ever changing. This is just another step
- JohnFen 8y agoWhy is it called "serverless" when it is not, in fact, serverless? It's petty, but that nomenclature drives me nuts.
- grzm 8y agoWhy do we park in a driveway and drive on a parkway? The key is to understand what people mean by the words they say. Yeah, there can be things that get under our skin, but at the end of the day, just roll with it. (I say this as much to remind myself as to you.) Looking for absolute consistency in language is a recipe for needless, self-inflicted frustration.
- JohnFen 8y ago"The key is to understand what people mean by the words they say." Yes, it is -- and I'm not entirely sure I understand what "serverless" means when used this way, unless it's just a term that marketing people invented because their old term "the cloud" has lost its sizzle.
- dragonwriter 8y ago> Why is it called "serverless" when it is not, in fact, serverless? It is serverless from the perspective of an IT department that, by adopting it, no longer has to manage servers as a distinct resource. It's like a product sold as having “worry-free interoperation”. There's still worry in the interoperation, you are just paying someone else to do the worrying. Likewise, a serverless product still has servers underneath, you are just paying someone else to abstract them so that they aren't a concern for you.
- jdietrich 8y agoThe Serverless framework is platform-agnostic and open source. You can use a bunch of different FaaS providers, or self-host on Kubeless or Fn. https://serverless.com/ https://serverless.com/
- jedberg 8y agoThere is absolutely no lock in whatsoever with Lambda. The features provided by Lambda are also provided by Google Cloud Functions and Azure Functions. The lock in comes from the ecosystem you use them in. If you make code that just returns the time, you can run that anywhere. If you make code that uses a database, your database choice provides lock in, but not Lambda. And it's the same lock in you get using any service from AWS. But your trade off is that you can make something that's super portable, but must cater to the lowest common denominator of features amongst all the providers you want to be compatible with. I'd rather have lock in than be hamstrung by the velocity of the slowest provider.
- time0ut 8y agoI've built a number of serverless systems over the past few years on AWS and GCP. None were too extreme, but ranged from moderately complex SPA to silly chat bot. Some saw light, but real, usage. To echo what others have already said: the lock in isn't in the compute, it's in the ecosystem, which also happens to be where all of the value is. Like everything else in our industry, serverless is a series of trade offs. There are a number of classes of problems where it is absolutely worth trading the downsides of serverless for the agility and velocity the ecosystem can provide you. As with anything, the key is knowing when it is the right tool and how to use it properly.
- softwaredoug 8y agoThere’s a whole generation of developers that didn’t come up in IBM and then later MS days of vendor lock-in. Open source is default and it’s easy to only see the benefits and positive side of one vendors vision. Only now it’s harder as proprietary tech is often cloaked in “open” culture and only when you go to rip the bandaid off do you see where the real lock-in is
- lbacaj 8y agoAt the expense of losing what little reputation I have on HN I will say this: As many others on here seem to be correctly saying, i think this article amounts to fear mongering of vendor lock in. The modern public cloud is very different from the Oracle/IBM mainframes of yester-year. The whole point of the public cloud is to leverage managed services to their fullest extent so you can move incredibly fast. As a startup, you’ll run laps around your competitors doing all of this from scratch simply to preserve their non vendor lock in. The notion that removing that glue code that glues your code to AWS or Azure managed services amounts to vendor lock in, that is no more true than any other code running on any VM that talks to those same managed services. Except the main difference here is that your not wasting time writing the glue code. Additionally Azure Functions or AWS Lambda, or even Functions on Kubernetes, which are meant to be the smallest unit of work when used correctly (similar to a MicroService) and should contain only your application logic are “vendor lock-in” is absolutely rediculous to me. If anything when you do decide to move vendors this will be the easiest code in the world to migrate, inputs and outputs. I will concede that it is hard to see this the way I’m describing if you haven’t actually worked on the modern public cloud and are not actively taking advantage of managed services on there for speed of delivery. A little self promotion: as an example of what’s actually possible with these Serverless frameworks I recently built a cross platform app, as a side project in just a few months nights and weekends with the entire backend as Serverless Functions, the app can read any article to you, using some open source ML models for text to speech, and can be found https://articulu.com https://articulu.com if you want to check it out.
- tyingq 8y agoI would guess ecosystem as a whole is a bigger deal. Porting lambas alone probably isn't a huge deal. But then the cloudformation templates, sqs configs, dynamo tables, rbac configs, S3 access settings, cloudwatch logging and alerts, etc. It all adds up.
- CyanLite2 8y agoLock-in concern in the cloud is an antipattern. Only way to solve it is to go on-prem and manage everything yourself. In the meantime I'll enjoy super cheap S3 storage rates. If AWS ever goes out of business then I'll worry about that then.
- WrtCdEvrydy 8y agoAWS won't go out of business. You'll start seeing slowly increasing rates... and as people leave, the rates will increase further. Eventually, you'll start seeing Snowball no longer supported for getting your data off S3.
- deleted 8y ago[deleted]
- peterwwillis 8y ago> He elaborated: "It's code that tied not just to hardware – which we've seen before – but to a data center, you can't even get the hardware yourself. And that hardware is now custom fabbed for the cloud providers with dark fiber that runs all around the world, just for them. So literally the application you write will never get the performance or responsiveness or the ability to be ported somewhere else without having the deployment footprint of Amazon." It's almost as if you're paying to use someone else's massive investment in technology so you don't have to reinvent the wheel, enabling you to just get business done quickly and at ridiculous scales. Kind of like using Windows tech stacks, or buying a Ford F-350. Who could possibly build a business on such terrible lock-in devices?
- forrestbrazeal 8y agoSerious question for all on this thread: have you personally encountered a deal-breaking issue while actually implementing a significant application on "Lambda and serverless"? Whether that's lock-in, scaling issues, cost, performance, or whatever. Has there been something that's caused you to go "yeah, no, this was a bad idea; should've rolled my own infra." I'm not asking this disingenuously; I legitimately want to know.
- galaxyLogic 8y agoWhat about hybrid cloud? Wasn't that supposed to solve the problem?
- Brahma111 8y agoClear abstraction anyone? We make it mandatory to separate the Managed service code to separate interfaces and implementation. We have the same code running both on Azure and AWS each leveraging their respective managed services. Just implement the interfaces for your need. It's not difficult.
- staticassertion 8y agoThe argument makes no sense. Because it is deployed in AWS, you can't get performance without using AWS services, therefor it is locking. This seems like no more of a lockin than, say, choosing a DNS server that's giving me lower latencies. My AWS Lambdas talk to a Postgres database, S3 (which has many open source API implementations), and SQS, which yeah, I'm "locked into". The work to move to another service would be absolutely trivial. All of the AWS stuff like Postgres, S3, and SQS is totally abstracted from the business logic. I could rip it out at any time. I just don't get what anyone means when they saw lambdas lock you in, I don't feel locked in at all. I could move to GCP in, idk, two weeks probably.
- stcredzero 8y agoI am thinking of my own SaaS offer, but combined with Open Source. Basically, you will be able to publish a certain kind of application with a little bit of Javascript coding, and coding several lambdas in Golang. There will be an entire miniature server cluster running as goroutines, which you will be able to download off of github, then run locally. You will also be able to take the same server cluster and run it on a service like AWS. (On my roadmap, I'm going to remove all dependencies outside of the project, so you will pretty much be able to fill out the config file, and just run the executable, and have it scale according to the number of processors. However, you will also be able to sign up for an account on my website, then use a command line facility to "inject" your lambdas into my system, which takes care of the autoscaling, database backup, and staging for you.
- gjmacd 8y agoarticle is from 2017, AWS has EKS (Kubernetes)
- asaddhamani 8y agoZeit is a great alternative here in my opinion. You don't need to make any changes to your code, it will just run on Zeit. Have used it to host a few microservices in the past and the experience has been much more pleasurable than Lambda (I needed to do PDF generation through a browser and had to use Zappa and modified binaries for phantomjs)
- gigatexal 8y agoIs it lock-in? It’s just your code being packaged in a container and run on an api invocation. I thought one could move from any of the big three’s serverless function offerings pretty easily?
- quickthrower2 8y agoOn Azure it's not a docker container, or any other kind of 'standard' container. That said you can get a docker container with the Azure Function runtime, so you could in theory port your functions elsewhere, but I don't think you get the monitoring benefits that you'd have keeping it on Azure.
- deleted 8y ago[deleted]
- cwyers 8y agoI have worked with database code that was meant to only work with the database it was running on, and database code that was meant to be agnostic to what database you used. I always thought that the costs of the second were underappreciated relative to their benefits. And unless you're actively maintaining running on more than one database (as in, shipping a product where your users have more than one database) you tend to miss all the implicit ways you come to depend on the implementation you're on -- yes, the syntax may be the same across databases, but performance impacts are different, and so you tend to optimize based on the performance of the database you're on. I suspect the same is true for cloud. Real portability has real costs, and if you aren't incurring all of them up front and validating that you're doing the right things to make it work, then incurring part of them up front is probably just a form of premature optimization. At the end of the day, all else being equal, it's easier to port a smaller codebase to new dependencies than a larger one, and attempting to be platform-agnostic tends to result in more code as you have to write a lot of code that your platform would otherwise provide you.
- benjaminwootton 8y agoThe big difference with something like PL/SQL is that it’s a proprietary language, whereas lambda and the other faas options are based on open languages. Makes portability somewhat easier to achieve.
- Cthulhu_ 8y agoFor sure; the external interface of a lambda is trivial, that is, a single entrypoint function with an 'event'. It's relatively easy to create a simple wrapper around that to make it either provider agnostic or self-hosted.
- collyw 8y agoI haven't used lambda but it sounds remarkably similar to a Django function. In Django urls point to a function. Your request matches that url, that function gets run. Lambda must have some similar sort of mapping of urls to functions, so what exactly are you saving with it? Ok, Django includes an ORM, but if you are using any sort of persistence you will need a database layer as well. Can someone explain what all the fuss is about or what I am missing?
- jonthepirate 8y agoI wrote a flaky test management system called https://www.flaptastic.com/ https://www.flaptastic.com/ on AWS Lambda... my first AWS bill was $2.50. I love it. I also used serverless.com's wrapper to deploy it for free. If this gets expensive and I want to raise money to have expensive DevOps engineers setup Kubernetes for months then fine... but I really don't need that and I can easily port this to any other platform if I want to later.
- crb002 8y agoTotally disagree. It's a stock Linux container. The most transparent of all the "serverless" runtimes out there.
- acroback 8y agoSo are cloud APIs which lock you in. E.g tensor flow, Aurora and all that shiny jazz. Hate it, it is useless once you change provider or go bare metal. Cloud computing is Vendor lock in of 21st Century.
- byteface 8y agoIs using the features of a tool, 'lock in'? You could do the things the tool does yourself but you choose to leverage the tool. That's why you use it. You're aware of this. aws lambda functions can be just pure python or other code. Anything logged there can be a metric in cloudwatch. Users are blissfully aware of how much it's doing for them from security to monitoring. And to be honest companies with enough money would prefer these solutions to something you can knock-up yourself. I feel so locked in by my million free requests a month to service that wont choke that I didn't even have to set-up.
- pantulis 8y agoAnd that's why Knative is going to be a thing.
- sologoub 8y agoWhen discussing lambda/serverless/<whatever flavor of pay per request> setup, people don’t often seem to stop and think about the usage/access patterns, the associated costs and performance. I’ve seen such setups being recommended for APIs that have predictable and fairly constant load, for which you are a lot better off having an actual running set of processes that can be reused. For Google that could be AppEngine, for AWS ElasticBeanstalk. It’s a question of the right tool for the job. One tech that I haven’t played with that’s really interesting is KNative, where you can run an underlying infra with predictable costs/performance, but allocate it like a lambda per request. Performance of the requests themselves may still be less though when compared to a more traditional setup.
- captainbland 8y agoThe problem I see with this kind of vendor lock in is you can get screwed in several different ways if you let yourself get locked in enough. The 'good': a competitor overtakes AWS and is able to offer vastly cheaper or better value services than you have access to, rendering you less competitive than people who are able to move to that platform easily. The 'bad': Amazon starts deprecating services you rely on and you're forced to port things anyway. The 'ugly': Amazon decides that it's happy with its market share or its shareholders start demanding they bring in more revenue and they realise that those who are locked in to AWS are easy targets. It'd be easy to just jack up the higher tiers of things like lambda, dynamo DB, API gateway, etc. and on those who they have bespoke agreements with without even necessarily affecting their marketshare. It's really a risk/reward thing when going for these platform specific serverless systems. It's like asking if you trust a big company enough that you want to give up all of your bargaining power with them, and that you're going to put thousands or even millions of dollars where your mouth is on that.
- dhab 8y agoLike Oracle.
- scarface74 8y agoAs far as I know, in the entire existence of AWS since the first services launched in 2006, they have never abandoned a service.
- fdsak 8y agoWell, then why not standardize them ?
- rynop 8y agoI made the OSS https://github.com/rynop/aws-blueprint https://github.com/rynop/aws-blueprint partially to address this problem. Easily migrate from Lambda to ECS (remove lambda lock-in). It abstracts all the difficult & time consuming to learn aws idiosyncrasies in to a best-practice production ready harness. You could argue that if you have lots of lambdas, this is non-trival. I would argue that tons of lambda is a poor architecture. What you gain with isolation you lose management, complexity, nimbleness, attack vector surface. You could also argue my harness locks you into AWS as it is aws specific. However I'd argue that it is the other aws services locking you in (ex: Dynamo) or your code/architecture.
- flurdy 8y agoThis is why I can see why Kubeless [1], Fission [2] and OpenFAAS [3] are gaining traction. But my take is always that it depends on the size of your company, your cloud strategy and how much serverless you are using. * If you are small company dabbling in small serverless scripts, just use Lambda. * If you are a medium+ company but have gone all in on AWS or GCP, and serverless is still a limited small part of your stack, then also just use Lamda or Google Cloud Functions. But consider the options. * If you are a multi-cloud company or more invested in serverless. Then they are the ones that should definitely consider OpenFAAS etc and not use Lamda etc for anything but minute parts of your stack. * If you use Kubernetes and are fairly Cloud agnostic, then use Kubeless etc so that you have full serverless support in local and staging clusters and any cloud provided clusters you expand and migrate to as well. [1] https://kubeless.io https://kubeless.io [2] https://fission.io https://fission.io [3] https://www.openfaas.com https://www.openfaas.com
- nzoschke 8y agoIf you want to see what the “lock-in” actually looks like check out: https://github.com/nzoschke/gofaas https://github.com/nzoschke/gofaas It’s a boilerplate Go, Lambda, API gateway, dynamo, SNS, x-ray etc app. Personally I embrace the “lock-in”. This architecture faster, cheaper and more reliable than anything I’ve seen in my 15 years of web development. Most importantly it is less code. Most time is spent writing Go functions. A little time goes into configuring the infra but the patterns are simple. No time goes into building infra or a web framework. I think Go is the antidote to true lock-in. I have a ‘Notify’ function that uses SNS that I recently replaced with a Slack implementation. With well defined interfaces you can swap out DynamoDB for Mongo if you have to move. It is also easy to turn a function into a HTTP handler. There is a smooth path from function to container to server if the cost or performance of lambda doesn’t work. It’s hard or impossible to go the other way.
- johnklos 8y agoSigh. "Serverless" is the most ridiculous example of bullshit marketing in recent history. It truly took me a good twenty minutes to understand what it is supposed to represent because I kept thinking, "There HAS to be more to this than vendor-supplied CGI." People make many arguments for designing WITHOUT portability (and cwyers even calls portability "premature optimization"). What they're implicitly stating is that they can't code to abstractions, aren't effective at coding without using edge cases, and require package specific optimizations to barely get acceptable levels of performance. If the edge cases and package specific optimizations weren't considered necessary, there'd be no real case for making something non-portable. The fact that people can even rationalize non-portability boggles the mind. It just seems like a poor attempt at job security or something equally silly.
- tracker1 8y agoWorth mentioning that CoreOS was bought out by RedHat, which makes a lot of sense given where they were going with OpenShift. Which, in turn was bought (is being bought) by IBM. In the end, the tooling in use is crossing a lot of lines and becoming very common in a lot of ways.
- aussieguy1234 8y agoApache Openwhisk https://openwhisk.apache.org https://openwhisk.apache.org. it's open source and can run on any cloud platform. It will run your serverless apps. You'll maintain some infrastructure to run it on unless you go for a hosted service like IBM provides. I'm building the infrastructure for Libr (Tumblr replacement, https://librapp.com https://librapp.com) on a serverless platform that I won't name which will be hidden behind a reverse proxy. There won't be any vendor lock in. It's an express/Vue app and will run on any serverless platform or CDN. If the app is censored by my first cloud provider (perhaps due to pressure on the provider from SESTA/FOSTA) I'll move to a new one. It's likely I'll build parralel copies of the production infrastructure on different cloud providers at some point for rapid migration capabilities.
- legend_sam 8y agoI think that's the exact reason why people came up with Kubeless. https://kubeless.io/ https://kubeless.io/ It doesn't have to be vendor locked. You can literally host the k8 cluster in your local