4 ms·
Are servers really that hard to manage these days? This seems like way more work and pretty limited in what it can really do, especially compared to a few lines
by manigandham 11y ago
Are servers really that hard to manage these days? This seems like way more work and pretty limited in what it can really do, especially compared to a few lines of code in any decent web framework that can perform a lot faster.
- motoboi 11y agoI think biggest news here is the possibility to share a server with someone else, with amazon acting as a broker of CPU time. With virtual machines, we started to share physical resources which were otherwise wasted in dormancy. But even virtual machines were a waste of resources, as you need someone to set them up, keep them online and working. What if you could share the money you spent with those people and their knowledge? Amazon just did that to you. All some people want is to run code somewhere on the internet. Amazon gather them together to share a server and an admin team. In my point of view, Amazon Lambda is a huge improvement in efficiency for people around the world, as I (or someone else) can pay for a very tiny part of the work of a very specialized sysadmin and focus on my code.
- manigandham 11y agoYea I can see that. Lambda is cool and there are some niche cases where it's useful... However when talking about microservices, any non-trivial app quickly gets extremely complicated to setup and actually more inefficient in the amount of time it takes to execute each request. And probably more expensive since there still have to be servers somewhere, always ready to run your app and with all the management and orchestration layer on top. Also VM technology is sufficiently advanced that they can be multitenant on the same base hardware very efficiently and consume almost no resources while in a sleep state. With live-migration and auto-scaling advancements it's not a big deal.
- twic 11y agoIf your scale is small (you're in the 'two people in a garage' phase of your company), then the cost of having your own server is small, even though you waste most of it. Hetzner will rent you a real physical server with an x86 processor and 32 GB of RAM for about 40 euros a month. I'm sure you can get smaller virtual servers elsewhere for less. If your scale is large, you have enough work to make full use of however many servers you rent. Reducing infrastructure waste at small scale seems pointless to me. The actual cash money saving is just lost in the noise. The only way i can see that i could be wrong is if there's a suppressed demand for huge numbers of tiny-scale services. Is there?
- Goranek 11y agoIt doesn't matter if you are big or small, you're always wasting resources.. Just count how many servers you have using <50% cpu. By having thousands of users, amazon can organize servers in a way, no cpu is wasted.
- brianwawok 11y agoIf they kept CPUs 100% busy, how would they deal with a surge in demand or a failure situation? You HAVE to keep spare capacity or 1 failover crashes your entire fleet of 5 billion servers. You could correctly argue that usage increases with scale.. so while you with 1 app can maybe only keep a server 20% busy, Amazon can afford to keep their servers 70% busy.. which is part of the story. But the other part is you are paying for the convenience. You can get raw CPU way cheaper than what lambda gives it out at. Even if you only kept your CPU usage at 10-20% - for example Digital Ocean would still be cheaper than the Amazon Lambda app version. You are literally paying a surcharge to not have to set up your own servers, or deal with maintenance. I find it very unlikely you will save big money with lambda over your own servers.
- brianwawok 11y ago> Reducing infrastructure waste at small scale seems pointless to me Agreed. I think what it avoids though is setting up ansible + puppet + firewall + updates + monitoring + blah blah stuff you do to secure and dev-ops a prod app (for a baby app). You can half-arse this stuff in a day for a new company. I assume the defaults of lambda will be a little more secure... but amazon security is pretty complicated to set up right, so not totally sure what the max win will be.
- spdustin 11y agoMy scale is unpredictable. I don't sell software, I sell consulting and training services. To make our business run smoothly and maximize the available time of the two of us who run the place, we can't be held down by managing servers and services. Investing in things like API Gateway and Lambda gives me the ability to keep my programming desires satisfied, while reducing the friction of tedious, time wasting operations, like automatically encoding a video of a class, extracting thumbnails, and setting permissions via API calls back to our home-brewed DAM system to make the video available for our students. Sure, I could do it myself each time. Six times per day of teaching. And turn down the process priority so it won't interfere with the rest of my job. The costs of using AWS at that scale, while certainly nothing like the scale some of you are dealing with, are a considerable savings over the hourly rate I can charge for the time spent in my subject domain, and would have otherwise lost. We manage VMs for classes already, and most of that is now automated by our Hubot. In the coming weeks, the services/sites/apps we do have running will be migrated over to the docker-based infrastructure I'm building (in my copious free time, ha!), and the services therein will be interconnected with API Gateway and Lambda functions. It's a beautiful thing. I'm really quite pleased with it, and proud of what we've been able to do. I'm know that I'm not alone, and maybe this post will encourage others in similar situations to share their experiences too. Maybe my peers don't frequent HN - that's an unknown to me, I guess. But there are far more entrepreneurs like me who enjoy the job we do, and will do everything we can to offload the time sucking administrivia to some other system, especially if we get to flex our programming muscles along the way.
- dragonwriter 11y agoThat kind of server sharing is exactly what all cloud platforms (IaaS, PaaS,etc.), as opposed to dedicated servers, are about. And that without having to set up virtual servers on an IaaS like EC2 isn't new, lies of people, big and small, were doing PaaS offerings long before Lambda.
- zoul 11y agoFor me as a mostly one-man show, yes, having a server to manage is a pain. Investing some extra time into a “serverless” solution is greatly preferable to managing a server. And if not anything else, with a server you always have at least extra security to take care of.
- manigandham 11y agoWhat about the PaaS like elastic beanstalk or heroku? Are you coding an entire app using Lambda?
- zoul 11y agoTo clarify, I don’t currently use Lambda at all. But generally speaking, any service that doesn’t require me to maintain a server is a plus (Beanstalk and Heroku included).
- wpietri 11y agoI personally have an old-school ops background, so for me managing servers is fine. However, I just had to drag some of my colleagues through an explanation of the infrastructure I set up earlier this year. For them, it was about 80% irrelevant ops-ish details versus 20% stuff they actually cared about. And I get it. They shouldn't have to care. The whole notion of a "virtual server" is basically like saying, "radio with pictures" or "horseless carriage". It only makes sense in a specific historical context. We're still figuring out what comes next, but I think it's safe to say that 20 years from now the main building block will be something different than the simulation of a 1970s university department minicomputer that we're all using now.
- sampl 11y agoLove that analogy
- herval 11y agoIf you're a single developer/small team with a very small product, managing servers is a chore that won't add any value to the product you're building. So you either spend very little time on it and build servers adhoc ("snowflake" style - SSH in, install some stuff, etc), or you spend precious time doing "the right thing" - which right now is a huge universe of options (Chef/Puppet/Ansible, Docker/other containers/no containers, etc). If you're part of a larger team, not having a properly structured infrastructure is a nightmare - specially when it comes to scaling or dealing with failures of all kinds. TLDR; - yes, I'd say it's somewhat hard...
- joeyspn 11y ago> I'd say it's somewhat hard... I don't think it's hard, it's just time consuming. And we all know that "time is money", specially for small teams or solo devs (as you pointed out).
- herval 11y agoDoing it right is hard. Scaling infrastructure throughout multiple zones while keeping data as consistent as possible, deployments as easy as possible and having as few SPOFs as possible is pretty difficult (and done differently by every single team). The range of things that can go wrong is huge...
- joeyspn 11y agoNot every product needs AZ from the start (specially for small teams or solopreneurs), in most cases you'll be doing over-engineering. And in the use cases you need AZs and do it right new tools like convox* are really easy to use and can save you a lot work. It's never been this easy to manage your own infrastructure. During the years I've used ssh, puppet, fabric, ansible, capistrano, cloud formation, etc for managing servers and infrastructure. And I think that the main benefit of any PaaS, AWS Lambda or AWS API Gateway is (obviously) that they're time saving and abstract the internals. In fact I use them in several small projects. * https://www.convox.com https://www.convox.com
- 11y ago