5 ms·
Ok, I have seen the phrase "serverless" a few times recently. Can someone explain to me what it is (as I am pretty sure it involves a server - it runs on AWS ff
by collyw 10y ago
Ok, I have seen the phrase "serverless" a few times recently. Can someone explain to me what it is (as I am pretty sure it involves a server - it runs on AWS ffs) and why I should want to use it?
And most importantly, is it web scale?
- Slippery_John 10y agoIt just means you don't have to worry at all about managing the servers, using thing like AWS Lambda which handle it for you. Generally these services will scale up and down for you as well.
- oneplane 10y agoThat just worries me all the more. You basically get software engineers that wall themselves into their garden. It's like nodejs all over again...
- nostrademons 10y agoThat's been the trend in the software industry since about 2000. When I started then, the job description was just "software engineer", and you were expected to know networking, databases, low-level code, UI code, scripting, etc. Now you have "frontend software engineer", "backend software engineer", "full-stack software engineer" (which seems to mean web framework + database, which is a very different meaning from what "full stack" meant when I started, or what it means at big companies like Google), "AWS specialist", "web developer", "Android developer", "iOS developer", "SRE", "devops", "data scientist", "machine-learning researcher", "infrastructure engineer", etc. It's actually a boon to entrepreneurial types who really do know the full stack inside and out. So many startups these days are "slap a web or mobile app in front of a manual process", so people who really do understand computation and all the things computers can do have less competition.
- scardine 10y agoIf you don't understand why GOOD startups do this, take a look at the "Doing things that don't scale[1]" lecture from "How to Start a Startup" series by Sam Altman at Stanford. [1] https://clip.mn/video/yt-oQOC-qy-GDY https://clip.mn/video/yt-oQOC-qy-GDY
- deleted 10y ago[deleted]
- losteric 10y agoWe're still figuring out how to separate responsibilities for building software... it's the same cycle of maturation that construction, manufacturing, and every other large domain goes through.
- audleman 10y agoI think this type of thing will end up being useful for special cases, but in general we'll still want to run our own servers. Their use case of creating a public API is a great one: it's a simple interface and having Lambda handle the auto-scaling is pretty awesome.
- coredog64 10y agoWe are using Lambda to export CloudWatch metrics to another system. Haven't exceeded the free tier of Lambda yet, and CW itself was only $5 last month. Having a t2 up the whole time would have been way more, plus it would have been subject to our Chaos Monkey.
- oneplane 10y agoWouldn't it be a lot cheaper if you have a dedicated box where you can run your own VMs and add and remove services as you please? So far, running one at base cost with leased hardware costs about 1/10th of any 'cloud' provider out there, with lots more resources to go around. Right now, if want to spin up a new instance, container or process, I can do it locally, in vagrant or on a VM on the dedicated box all with the same config and management ease of the configuration management stack (we use SaltStack). It also works just fine with stuff like GCE or AWS, but those simply are never ever the 'cheapest' option. At best, they are a in-between solution when we need more hardware. It's great for temporary scaling, but of nominal resource usage there is no point in using those services at all, at least for us. The cost of a dedicated box is static, no matter how much you use, and yet it is always lower than the mean cost or 95th percentile of any AWS/GCE kind of thing. For (converted currency from euro) about 100USD we get 16 E5 cores, 92GB RAM, 1TB SSD RAID10, 10TB HDD RAID10 and 8TB transfer on a dual 1Gbit link. For the life of me I can't find any combination on Amazon to match that.
- dkarapetyan 10y agoIt's just marketing hype. As you noted there is no such thing as serverless. It is another architecture that forces you to use AWS Lambda and API gateway and a few other services to glue everything together. The idea being that if you are just shuttling bytes back and forth then the overhead of the traditional deployment is too much and you're better served with what looks like an event bus with some transformers sitting in the middle.
- collyw 10y agoIt seems like its a serverless pricing model.
- meddlepal 10y agoIt means it runs using AWS Lambda and allows access via the API Gateway... it's literally in the second sentence with links to explain what those technologies are. Lambda's are just units of code that run only On-Demand and without having to manage one or more EC2 instances or a container platform.
- oneplane 10y agoAlso known as: an expensive and lazy way to make something work 'a little bit' until it gets too complex and times out.
- softawre 10y agohttp://martinfowler.com/articles/serverless.html http://martinfowler.com/articles/serverless.html
- dragonwriter 10y agoIn this case, its the FaaS version, which is really just a slight twist on traditional PaaS. Really, the "serverless" term does more to obscure than to illuminate.
- vhold 10y agoWith Lambda you pay per 100ms / per-1-million-requests. So, yes, it's very proprietary at the moment, but for any service that sits idle most of the time it can be very cheap. https://aws.amazon.com/lambda/pricing/ https://aws.amazon.com/lambda/pricing/ If you were hosting something like a little message board for your friends and family, or something you are demoing to to possible employers, etc, it'd be borderline free, but available all the time.
- jafingi 10y agoI have a SaaS running on EC2s/Beanstalk where I have a feature that a user only runs max. a few times per day (if any). It's a small Python algorithm that finds the most optimal combination in an array of items. For that, Lambda is great. We have lowered our price since migrating to Lambda for this relatively simple script.
- tie_ 10y agoIt means that you no longer have to deal with the server configuration - the servers are completely hidden from you. You just give your functions to AWS, and they run them in a black-magic-box of theirs. I've tested it at least to the extent of 100-200 rq/sec, and it holds up nice. Ultimately, there is a server somewhere, as you might expect. It's just not yours to manage/worry about.
- deleted 10y ago[deleted]
- wcummings 10y agoIt's an app server. It's like PHP.
- spriggan3 10y agoThat's exactly what it is, fancy CGI only one pays for each script execution instead of a monthly subscription. The "Oh, but it doesn't use HTTP but a pubsub architecture" is meaningless, that's still CGI for hipsters. And you still need to use (and pay) for API gateway on AWS in order to execute Lambda scripts from the outside.
- nashadelic 10y agoWell, if you look at how we've done things over the years: - We used to have our own machines in our own data centers - Then we started renting machines in data centers - We then moved to the cloud model where we would get compute capacity on demand. But the minimum unit was an hour - But what if you could deploy your code and you were only charged for the compute and memory you take for the fulfillment of that request? That is what the "serverless" model is. You don't constantly run a server like apache; instead, when you receive a user Request, the relevant function is called, executed and results returned to the user. You are billed for the ram ⨉ CPU. This has many benefits: - For low traffic sites, this has significant cost savings - For high traffic sites, this is auto-scaling without thinking about launching machine instances This isn't without problems, naturally. This lends itself well to certain type of problems better than others. For example, if you need lots of hot-cache data, the response times on a serverless stack would be slower. But as you can see from the above, this is the logical direction cloud computing will evolve. Infrastructure will truly be shared and you should be able to extract efficiencies down to the minute.
- Animats 10y agoIt's like running CGI on a shared server, except that it scales better.
- e12e 10y agoI wonder if that's really true (that it scales better than running more-or-less bog standard CGI across a fleet of thousands of servers, behind a load balancer). If I've understood lambda correctly, rather than spinning up a process (as with CGI), it spins up an entire vm/container. I suppose it might do the fast-cgi thing - spin up a container, and keep it running while there are requests coming in, and then kill it off. I'm sure there are other benefits of "container-on-demand" vs "process-on-demand" -- but I'm not sure "scales better" is one of them. Well, I'm sure it "scales better" in the sense of organization (human resources), but not necessarily in terms of machine resources. At any rate, I like the analogy.
- 10y ago