8 ms·
Function As A Service (FAAS) is so much of a better name than "serverless". I wish everyone would adopt it, and stop confusing everyone.
by nicoburns 8y ago
Function As A Service (FAAS) is so much of a better name than "serverless". I wish everyone would adopt it, and stop confusing everyone.
- Waterluvian 8y agoYes! I've been advocating among my colleagues to perceive "serverless" as "functional programming -> web services" I get that the allure of not focusing on infrastructure, scaling, etc. is strong. But that's really a side effect of what you're actually doing: applying FP principles to web service design. And it really fits the paradigm well. You've got HTTP services (short lived, therefore comfortably stateless) that are ideally infinitely scaleable (easy to do when your HTTP services are basically pure functions). Do you need caching? That's like memoization of your functions!
- scarface74 8y agoNo one who has any technical competence is “confused” by the term “serverless”. No one thinks that thier code is being run by unicorns and fairies. It’s more like people yelling at the wind or thinking they are intellectually superior because they are in on the little secret that servers are involved.
- manigandham 8y agoIt does cause confusion because it is absolutely non-descriptive, especially when the literal definition is completely the opposite of anything it has ever described. Pick a better term.
- scarface74 8y agoConfusion by who? I’m sure the same people who are “confused” by Amazon’s use of “serverless” would also be “confused” by terms like lambda, cloud formation, cloud trail, Redshift, Route 53, Elastic Beanstalk, Aurora, OpsWorks, Mechanical Turk, etc. Just like everything else in technology, if someone is confused by tech jargon, they should research it.
- manigandham 8y agoI'm sure you realize there are people out there that are starting out or are just new to this? There's no need to add to the confusion, we already have enough of it in this industry. Product names are either unique (for branding) or have some tangential matching definition. Serverless is none of those. Vague, inaccurate, nondescript. It is of no use. This is like NoSQL all over again, absolutely meaningless in every aspect and adding to years of
- scarface74 8y agoSo out of everything that it takes to be a competent dev in 2018, including learning $front_end_framework_of_the_week we should single out the term “serverless”? I know most of the features of AWS either from real world day to day use or at least on high level that I can talk intelligently about them. The time it took to learn them wasn’t lengthened by the term “serverless”. That was one of the easiest things to wrap my head around - write your code like you always do and just have a function as an entry point that takes two parameters - a JSON object and a context object and wire up an event that calls it. But on the other hand, when a bunch of Azure folks start talking about Azure features they are using, I am clueless. Does that mean that Azure services are misnamed or that I would need to spend some time learning about it on high level if I wanted to talk intelligently? For instance when I heard friends talk about Data Lakes, Data Factories, Event Hubs, I had no clue what they were yamerring on about. The same when anyone starts talking about machine learning.
- manigandham 8y agoNo. Who said single this out? Instead we should just do better. Concepts should be carefully named because this is not just jargon between a tiny handful of highly competent and super technical people; a vast number of devs and non-technical users will use these terms and it is in everyone's best interest to use descriptive and sensible wording. Data lakes, data factories, event hubs are product names, not concepts, but they are either exactly the same as their underlying concept, or very closely related. However, as stated for the 3rd time, serverless is not. It's completely inaccurate and vague. Where did you get that "serverless" means function as an entry point with 2 params? Every platform is different, from entry points to parameters, to bindings, to runtimes, to concurrency, to scaling, to security, and more. So the term is meaningless in describing anything. Many "serverless" function/lambda systems are evolving into running arbitrary containers and now have come full circle to basically a modern version of PaaS, which is what they should've been called all this time. There are clearly better options and tons of examples of poor naming causing annoyances and best and utter confusion at worst. We still live with the NoSQL hype repercussions and now serverless is following the same trend. It's not helpful and we can do better. What is a serious argument against that?
- jshen 8y agoServerless includes other things like google app engine and Heroku.
- mandelbrotwurst 8y agoDoes it? I always just considered those IaaS and thought "serverless" basically meant AWS Lambda or any comparable service (for which I agree FaaS is quite apt).
- hawaiianbrah 8y agoGAE and Heroku are considered PaaS - Platforms as a Service
- jshen 8y agoI think they are more serverless than PaaS by this definition. https://www.cloudflare.com/learning/serverless/glossary/serverless-vs-paas/ https://www.cloudflare.com/learning/serverless/glossary/serv...
- manigandham 8y agoCloudflare usually puts out good info but this is really bad marketing material stretched way too far to make a point, because they have their Workers platform and want to ride the "serverless" hype train. Everything mentioned in that diagram is completely arbitrary and varies for every single vendor.
- jshen 8y agoWhat’s a good definition of serverless in your opinion?
- manigandham 8y agoServerless doesn't have a good definition because it's not a real concept. At most lambda/workers/functions are really just PaaS, except instead of uploading all of your code, it's just a single file with a single endpoint. If we really need a new term, then micro-paas or FaaS works fine, although most FaaS vendors are expanding to running any arbitrary container with multiple endpoints, so we're right back to normal (but modern) PaaS at the end.
- tyingq 8y agoBetter than "hosted fcgi for hipsters" I suppose.
- rakoo 8y agoFaaS is closer in mindset to CGI than fCGI : if you're gonna have a server accepting connections, you might as well accept HTTP connections. CGI and FaaS are more like developing a function that transforms a request into a response, and let the infra deal with the rest. It is true though that it would be nice to have a standard for FaaS that doesn't have the inefficiency of CGI.
- icebraining 8y agoNah, it's FCGI because the process is kept "warm" and reused. It's much like the typical execution model of php-fpm.
- rakoo 8y agoThat the process is kept warm is an artifact of the infrastructure. As a Dev you absolutely don't care about how it's run and that's the whole point: just implement your business logic and the system takes care of the rest. As a dev it's all transparent.
- deleted 8y ago[deleted]
- icebraining 8y agoThat's actually less true of Lambda than of php-fpm. In Lambda, you can mutate the state of global variables between requests[1]; you have to take care not to do that. In php-fpm, all is thrown away. [1] http://blog.matthewdfuller.com/2015/12/aws-lambda-occasionally-reliable-caching.html http://blog.matthewdfuller.com/2015/12/aws-lambda-occasional...
- tyingq 8y ago
- staticassertion 8y agoServerless also implies 3rd party management and pay-per-use. Regardless, I truly can not wait to see a topic about serverless that isn't primarily bickering about the name.
- TeMPOraL 8y ago> Serverless also implies 3rd party management and pay-per-use. How does it do that? "Serverless" as a word implies no servers, and therefore no 3rd-party management, and no pay-per-use. Which is why the name sucks.
- staticassertion 8y agoIt implies those things because that's what it means?
- TeMPOraL 8y agoNah, that's a redefinition attempt that got out of hand.
- scarface74 8y agoNo it’s no more out of hand than any other term that has been co opted in computer science and that most people in the industry have sccepted like bugs, viruses, bits, etc.
- staticassertion 8y agoUh, what was the previous 'computer science' definition of 'serverless' ?
- scarface74 8y agoWhat was the previous "computer science" definition of "debug", "virus", "platform", etc. before someone coined it? But as time goes on, if you are part of the profession, when someone starts a conversation about the merits of "serverless", it's not helpful or insightful to keep with the tired response "the code is running on servers not via magic pixie dust". That response is about as insightful in 2018 as saying "I don't know why they are calling it debugging. Don't they know there are no physical bugs in their code"?
- p1necone 8y agoAgreed, "serverless" is a shockingly terrible name for all the things it's used for. Like, really really shockingly terrible.
- stevekemp 8y agoWe should go old-school, and call serverless-functions "CGI". It's not too far off the mark ..
- deleted 8y ago[deleted]
- dominotw 8y agowhy is serverless confusing? FAAS sounds like some api you can call to get functions. Maybe Function Execution as Service sounds better.
- manigandham 8y agoExecution is implied. What does "call to get functions" even mean? Would you think that PaaS means an API to get platforms?
- icebraining 8y agoWell, Joe Armstrong once proposed a global database of open source functions, that you could dynamically lookup and fetch [1]. Sounds like Functions as a Service :) [1] http://erlang.org/pipermail/erlang-questions/2011-May/058768.html http://erlang.org/pipermail/erlang-questions/2011-May/058768...
- stephenr 8y agoBecause it's not server-less. There is still a server running the code, you just don't control it. Claiming "it just means I don't have to worry about it" means that classic shared web hosting with shockingly outdated versions of php and perl are "serverless" too.
- dominotw 8y ago> There is still a server running the code Is there anyone who really thinks that there is no server anywhere. I find this complaint really odd. Your complaint can be applied to FAAS too, don't all webserver execute functions? What else would they be serving.
- stephenr 8y agoNon technical people? If you want to dismiss the literal issue, that means the name is meaningless. It might as well be called Daffy Duck.
- jasonlotito 8y agoServerless databases are a thing. Serverless is not confusing. It's only confusing if you try to be pedantic with remarks like "duh, it has to run on a server some where." Which really means wireless networking doesn't exist, because there are still wires involved somewhere, and I don't hear people being pedantic about that.
- deleted 8y ago[deleted]
- devwastaken 8y agoWireless networking is wireless because communication between device and AP is wireless. Serverless has no point where there isn't a server involved. It's just a service that runs your program on a server you don't control. No definition of 'serverless' fits into that.
- millstone 8y agoIf you think "serverless" is not confusing, then you have lost the vocabulary to even describe apps that run truly without servers: Photoshop, Word, tons of games, etc. By your "wireless" analogy I think you view these apps to be absurd impossibilities, like electronics without wires. This distinction is important. SimCity 5 gratuitously required the user to be constantly online, talking to some server. I mean obviously - there has to be a server somewhere, right? No, there does not!! We need to retain the ability to talk about apps that do not need ANY server, and "serverless" muddies that crucial distinction.
- icebraining 8y agoAgreed. And even web apps can be truly serverless, like TiddlyWiki.
- staticassertion 8y agoAre you seriously incapable of talking about programs that don't require servers because the word serverless exists? Have you considered... offline? Local? I've never heard the word serverless ever used to describe a system that does not require servers.
- daxfohl 8y agoJust remember the modern definition of serverless: 1. Not using a server. 2. Using a server. Not serverless. Problem solved.
- aikah 8y ago> Just remember the modern definition of serverless: Just because it runs on someone else's machine doesn't mean it is "serverless". an API Gateway obviously is a server. FAAS is just a good old worker queue, there is nothing new about that. There is no "modern definition" of serveless. it's just marketing, it has nothing to do with technology. Developers shouldn't use that word and expect to be taken seriously.
- olalonde 8y agoThat's a good definition for P2P, not for "serverless". Serverless functions run on a server. It typically refers to a category of PaaS which allows on-demand code execution (as opposed to "always on" services).
- icebraining 8y agoI believe the idea is rejecting that definition.