6 ms·
Containers won the battle, but will lose the war to serverless
- matthewmacleod 9y agoI hate to be all dismissive, but this is meaningless twaddle. I'm baffled that anybody with any experience of software development could think that something like FaaS will solve logic duplication issues; the hypothetical "118 systems doing pretty much exactly the same thing" exist because of organisational failures, and the same thing will continue to happen regardless of how that logic is implemented.
- zlynx 9y agoAnd if the organization does decide to have a "one official system" then it will need 118 option parameters or weirdly specific virtual functions in a base class and become a disgusting, complex mess. Because "pretty much the same thing" is not "exactly the same thing." Sometimes it can be hammered into place. Other times those differences were important. So yeah, I agree with you that duplication will continue to happen a lot.
- Macha 9y agoAnd sometimes this results in the 1 system being so complicated that it's less effort to build and maintain system 119 than hammer system 1 into a round hole.
- Nomentatus 9y agoThere are lots of things I won't bother to try to find at a corner store - sure they won't have the exact thing I need - and which twenty years ago I might even have tried to fashion for myself rather than make the rounds of downtown stores with equally poor luck; yet today I'll go look on Amazon, mostly finding what I'm looking for, and mostly ordering it. As the old military saying goes, "quantity has a quality all it's own." But Amazon doesn't just have that very large selection of goods, it has a financial motive for making that selection very well-organized and very easy to search and research (through reviews.) To revisit the example in the original article, it's very possible to believe your organization hasn't yet written a decent basic user registration function and still believe that it's overwhelmingly likely that someone else in the country, or world, probably has. Now add convenience and peer review, and you might finally be over the hump. Maybe.
- tlarkworthy 9y agoIt's replacing all the auth, provisioning, billing, load balancing, throttling and other crap. Sure you might still duplicate ur business logic, but at least no team is reinventing the serving infra
- seibelj 9y ago> Sure, it would be nice to have a competitive environment with different providers you can switch between. But that is secondary to usefulness and functionality, because companies are in competition with each other anyway. And the chance of getting the actual providers to agree is pretty close to zero. Everybody goes: “Well, we’re going to differentiate on this or that.” That is exactly the situation with kubernetes and containers, and it is nice indeed, as I can easily switch between providers. In fact, my company got free digital ocean credits and was able to seamlessly host a cluster on DO for free to enhance testing. This is the ultimate. What scares me about serverless is the complete lock-in with the vendor. It’s the same reason google app engine just couldn’t be a game changer. You need that balance between customization and commoditization that serverless I think fails on, unless some protocol like docker comes in to save it.
- zlynx 9y agoFrom 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.
- brutopia 9y agoThat’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.
- snowwrestler 9y agoIsn't "serverless" just a fancy way of saying "someone else's containers"?
- tluyben2 9y agoYeah, the whole serverless makes no sense. There is a server running probably in a container handling your code. Who came up with this weird name?
- CharlesW 9y ago> Who came up with this weird name? Amazon popularized it, but Ken Fromm's use is the earliest mention I've been able to find (from 2012): http://readwrite.com/2012/10/15/why-the-future-of-software-and-apps-is-serverless/ http://readwrite.com/2012/10/15/why-the-future-of-software-a...
- usaar333 9y agoWe were using the term serverless at PiCloud since 2010. Source: memory and https://www.techcrunch.com/2010/07/19/picloud-launches-serverless-computing-platform-to-the-public https://www.techcrunch.com/2010/07/19/picloud-launches-serve...
- tluyben2 9y agoI was discussing a project with a potential client ( I think they were called Threeships ) who used ActiveX and a lot of investment to create full p2p software and indeed serverless. Horrible tech that time but yes, that could be considered serverless; if there is a server (as in one physical or virtual machine handling multiple client software execution requests) it is not serverless. It is quite possible to let every client run their own request theoretically so you can make serverless but amazon is not.
- CharlesW 9y ago> Isn't "serverless" just a fancy way of saying "someone else's containers"? No, "serverless" just means that there are no servers (or VMs, or containers) to be directly managed by the developer.
- thinkpad20 9y agoWhen someone speaks in the style of this guy — absolute certainty of the superiority of their chosen technology, dismissive of or glossing over its disadvantages, condescending to those who use or advocate other technologies — it makes me very dubious of their claims. It also makes me assume they’re trying to sell me something.
- tyrankh 9y agoAgreed. This is clearly a fluff piece promoting his technology du jour.
- deleted 9y ago[deleted]
- zlynx 9y agoServerless really needs to work on their latency I think. Things will be going great and then there's the oddly weird 2 second delay. I guess it is bringing up a new server or container to run the lambda in. Whereas with your own (or well, Amazon's) machines you can scale up before hitting the limits and not need long pauses. Maybe one day they'll fix that.
- nstart 9y agoThis one's pretty important. I tried to implement slack commands using lambda. But because slack needs a first response within a tiny period of time, my command would often need to be run twice since the first attempt would timeout as lambda spun up the server.
- k__ 9y agoCan't you lower the latency of a cold start with less code?
- nstart 9y agoMaybe? All this code did was call another lambda function and return a 204.
- k__ 9y agoAh okay. I just watched a tutorial where someone described methods to make the cold starts faster and one major point was, get the code size down, because on a cold start the target machine needs to download the code and run it.
- StellarTabi 9y agoDepends on language, too. Python and nodejs's cold starts are close to 100ms, Java and C#'s can be more dangerous. I also assume that comparison was with minimal code samples with no dependencies.
- mankash666 9y agoThere are many connection oriented protocols that can never run on function as a service (Faas) offerings, which the article seems to suggest, is the only type of severless. Fundamental applications like email, webrtc, even git, cannot run inside FAAS. The future, in my opinion is offerings like AWS fargate. The developer writes logic that is containerized, and the auto scaling, scheduling, etc is handled in a seamless fashion by the provider, removing the burden of ops from the developer. In many ways, this is a connection-oriented Faas, and that is where the future likely lies, due to its wide applicability
- k__ 9y agoIsn't Lambda just the glue? I mean there is also Kinesis Streams, AWS IoT and such.
- olavgg 9y agoI really like the idea of serverless, in my use case a serverless setup would be great to run prediction on. For example a chatbot where you predict the intent. It would be a lot more cost effective than running the model on their own GPU/CPU instances.
- 013a 9y agoServerless is the future. But I doubt FaaS is. FaaS has a place, especially around latency-insensitive or bursty event handlers. But to suggest that it will replace any traditional server is pretty farfetched.
- k__ 9y agoAren't they working on that? I mean there is stuff like kinesis streams, AWS IoT and Lambda@Edge
- darkmarmot 9y agoHe's almost right! The Erlang VM (BEAM) will soon replace all the things :) (See Grisp: https://www.grisp.org/ https://www.grisp.org/)
- davesque 9y agoI'm just waiting until serverless platforms develop build scripts that create file system deltas to make deployments more storage efficient.
- vikiomega9 9y agoWouldn't version control solve this problem anyhow?
- davesque 9y agoWouldn't it be great if someone could figure out a way to express the logic that implements a function service as a compact, machine readable package which could be locally "cached" by all services that depend on it?
- EtDybNuvCu 9y agoTo quote from the interview, verbatim, "Sure, it would be nice to have a competitive environment with different providers you can switch between. But that is secondary to usefulness and functionality, because companies are in competition with each other anyway. And the chance of getting the actual providers to agree is pretty close to zero. Everybody goes: “Well, we’re going to differentiate on this or that.” The one exception, of course, being how everybody seems to have come together around containers. So now everybody’s excited about containers, but the battle’s shifted up. So you’ve won the battle, but lost the war." The interviewee here manages to make a Santayana mistake without realizing it; eventually, just as containers standardized, serverless functions will standardize, and cloud vendors will either conform or marginalize their offerings in response.
- wmf 9y agoBut by the time serverless is standardized he'll probably be pimping the next thing.
- marcell 9y agoI'm new to serverless, can someone clear up two things for me? 1. Can I run a standard Rails or Django app on "serverless"? 2. If I'm running on Heroku and don't directly manage servers, does that count as "serverless"?
- pronoiac 9y agoAnother name for serverless is function as a service, which might help clarify. No to both of your questions.
- tmnvix 9y agoZappa[1] allows you to do this (for python WSGI apps - I'm not sure if there is a similar option for hosting a Rails app serverlessly). I've found it very straight-forward to use for my Django app. I also like that if I choose to, I can ditch Zappa and host my app elsewhere (such as on Heroku) without really changing my app's code. [1] https://www.zappa.io/ https://www.zappa.io/
- pronoiac 9y agoHuh, I'd thought Lambda covered smaller components than those asked. TIL.
- moduspwnens14 9y agoYou can run Python WSGI apps (including Django) using Zappa [1] with a serverless infrastructure. Do you tell Heroku how many servers you need and how big they should be? Are you in charge of making sure you have the right number, or that the triggers for scaling up / down are working? If so, it is not serverless. [1] https://github.com/Miserlou/Zappa https://github.com/Miserlou/Zappa
- dominotw 9y agoIts not about 'directly manage servers' i think. You still have a conceptual view of a single server(rails server) that is serving your requests. In serverless you have bunch of servers that are serving requests for all apps that are deployed to them. Your specific app is not pinned to a conceptual server.
- ErikAugust 9y agoLambda is somewhat standardized and competitive - if you look at the Node API for example - you can port your endpoint to Express or Koa in 20 minutes. You aren't locked in by any means.
- k__ 9y agoYes. You just need a tiny wrapper to convert your Express endpoint to a API Gateway Lambda.
- jaequery 9y agoI was actually skimming his article to see if he mentions decentralization or blockchain somewhere.
- whalesalad 9y agoThis is like claiming cars will lose the battle to planes. These technologies are not mutually exclusive.
- k__ 9y agoGood to know. Wanted to go full-stack this year and decided to try "serverless", lets see how it goes :D
- alphaalpha101 9y ago'Serverless' has to be the stupidest idea I've seen in a long time. How could it POSSIBLY be a good idea?
- shadowmint 9y agoHe's right (in some ways). I know it's written in an irritating style, but I feel like this kind of scaled application deployment strategy is basically the future, and you'd be very very naive to dismiss it as just some marketing hype. The ability to deploy arbitrary micro-services to a cluster is basically all this is, under the hood, and that's something that intrinsically beneficial. Sure, you may argue, the difference between deploying code to a cluster, and deploying a container to a cluster may seem immaterial, largely, but ultimately its hard to argue that it's better to choose the container in most cases, if you can delegate the work of 'configure and manage the container and container infrastructure' to someone else. There's no question it'll slowly start eating the container world in my opinion; the barrier to entry is low, and ultimately (with something like openwhisk) you can use a container if you do need to package say, a specific version of opencv for some specific purpose. Can anyone suggest why this is a bad approach? It doesn't sound like a bad approach to me, and a lot of people are taking a lot of interest in it. The problem is the people who are pitching "microservices as a service", as though you might be able to delegate some parts of your service out as a microservice to other people, like you can run a 'lpad service' and there will be the new 'microservice app store' and people will all flock to use it, and a few people who write the early 'good functions' will Get Rich Quick. ...and every time any single one person screws up their service, or has a tizzy and shuts it down, dozens of applications will fail. What a disaster waiting to happen; its ridiculous, and all the noise about it is just people looking for funding (or just clueless, I have no idea). ...but, that doesn't change the fundamental value proposition of serverless: auto-scaling without devops. (Also: > And we’re seeing the exact same pattern with serverless. Yes, other companies could challenge Amazon’s dominance. But they probably won’t, because they don’t believe it’s for real. And by the time they do, it’ll be too late. Yep. That's spot on as well)
- ilaksh 9y agoIf they are talking about AWS Lambda-like stuff or just using 3rd party API services.. there are very obvious advantages to doing things that way over managing containers or VMs. Of course lots of people will still be using containers and regular VMs for quite some time just because it will be more practical for awhile for their use case or just out of familiarity. But anyway I think that eventually the real 'serverless' will be peer-to-peer systems like Ethereum smart contracts, IPFS, dat, etc.