12 ms·
I don't buy into serverless. I went to a webdev convention, and it ended up being a serverless hype train. Industry experts with a financial incentive to promo
by nicbou 6y ago
I don't buy into serverless.
I went to a webdev convention, and it ended up being a serverless hype train. Industry experts with a financial incentive to promote serverless went on stage and told me they can't debug their code, or run it on their machine. They showed me comically large system diagrams for very simple use cases, then spent an hour explaining how to do not-quite-ACID transactions. Oh yeah and you can only use 3-5 languages, and each import statement has a dollar amount tied to it.
More importantly, all those skills you develop are tied to Amazon, or some other giant. All the code you write is at their mercy. Any problem you have depends on their support.
Am I supposed to bet hundreds or thousands of man hours on that?
- sippingjippers 6y agoAWS in particular seem to have a carefully refined technical sales/certification/advocacy channel whose main product is those fucking stupid architecture diagrams. Hello world service with $4000/mo. worth of geo-replicated backing databases, CloudWatch alarms, API Gateway instances, WAF etc. But don't let it encourage you to think serverless has no value, or it can't be done portably or cheaply. It has its sweet spots just like everything else.
- diggan 6y agoReminds of something that was on the HN frontpage some month ago, where readers are not sure if it's a parody or not, because of the architecture you're required to deploy yourself to use this new "Perspective" product. Direct link to the architecture, that in the end serves the use case of generating a diagram of your AWS resources: https://d1.awsstatic.com/Solutions/Solutions%20Category%20Template%20Draft/Solution%20Architecture%20Diagrams/aws-perspective-architecture-diagram.f67026185e4f02d2d623289fa714d69d2c1f7af6.png https://d1.awsstatic.com/Solutions/Solutions%20Category%20Te... https://aws.amazon.com/solutions/implementations/aws-perspective/ https://aws.amazon.com/solutions/implementations/aws-perspec... https://news.ycombinator.com/item?id=24552779 https://news.ycombinator.com/item?id=24552779 (regarding costs, this setup ends up being +$500/month, again, to draw graphs of your architecture https://twitter.com/der_rehan/status/1308242717307174912 https://twitter.com/der_rehan/status/1308242717307174912)
- deleted 6y ago[deleted]
- deleted 6y ago[deleted]
- joana035 6y agoReading this made me remember that back in the day the AWS selling point was "here you can create virtual machines with few clicks and have it instantly instead of waiting 30 min for you colocated server to be ready" but now it seems to be "here is a bunch of random expensive tools, please, produce as much stuff as possible and share the word that having servers is bad™". This field used to be inspiring, but now I see the ideia of having a server being sold as the plague and lots of negativity towards people who are good at servers. They are not seen as another human being but the "other". Also I can't understand why one would prefer to pay that much for such complexity. It seems unsustainable for me, not to mention the new generation being spoon fed that that is way to go makes me concerned about the future of open computing.
- liv-io 6y agoYour response made me smile. Glad to see there are still reasonable folks out there. Working for a startup without a "resume-driven-development" CTO gave me the freedom to go "servermore" architecture with max flexibility.
- daxfohl 6y agoFor all the talk about resume driven development, I am hiring now, and will say that people who have solved their problems by learning more about Linux and such sound way more impressive than those who list out passing familiarity with a bunch of high level services. The first style of resume really stands out. The second is a dime a dozen. To make an analogy, it's like hiring a carpenter based on the number of tools they have. NO. Show me your skill with a hammer and chisel, and I'll assume you can figure out the rest.
- jasonlotito 6y ago
- beagle3 6y agoIt reminds me of https://www.frankmcsherry.org/graph/scalability/cost/2015/01/15/COST.html https://www.frankmcsherry.org/graph/scalability/cost/2015/01... - you pay an extremely high cost upfront without even noticing - for the promise that at some point, you'll be able to scale out to any scale, with no extra human effort and for costs proportional to the scale. I have not observed enough uses of serverless I can draw conclusions from, but if it's anywhere like hadoop style scaling, 95% of the users will pay 10x-100x on every metric without ever actually deriving any benefit compared to a non-distributed reasonably defined system, and 5% will actually benefit -- but everyone would want to put it on their resume and buzzword-bingo cards.
- m_mueller 6y agoIt depends. Give you an example: We have an expensive reporting workflow that needs considerable resources, but usually only once a month. Two ways to do this cost effectively: Scale down containers to zero, meaning several minutes of response time if you do need it ad-hoc sometime. At least as complex to configure. OR you fit it to AWS SAM. The latter has proven to be a good match for us. I solved the debugging story by keeping lambda functions AWS agnostic and wrapping them i a Flask debug server - will respond exactly the same but it is all local in a single process.
- rytemporal 6y agoI’m the head of product for Temporal. You should check us out, have to self host (MIT) right now but we are working on a cloud. You can safely write code that blocks for years. No more job queues.
- beagle3 6y agoI suppose you mean temporal.io, but just FYI, the first google result for me was https://github.com/RTradeLtd/Temporal https://github.com/RTradeLtd/Temporal which is far but not far enough to be “obviously unrelated”. You might want to give a link next time to avoid ambiguity.
- davidgatti 6y agoWell, only because you had bad teachers doesn't mean the topic is bad. You had the misfortune to interact with people that don't understand the topic they try to explain. I try to give a simple explanation here: https://consulting.0x4447.com/articles/knowledge/should-i-go-all-in-with-serverless.html https://consulting.0x4447.com/articles/knowledge/should-i-go... - just as a starting point to at least get a frame of reference when to use and not to use Serverless. But hey I'm just a random person in a random location on this planet :)
- raxxorrax 6y agoI bought into hosting stuff on AWS, specifically on EBS which I assume is meant by a 'serverless' infrastructure, but I don't know crap about it. Still think it is mostly awesome and the services are solid. But such infrastructure comes with its own caveats. EBS now bugs me about some 'HealthCheckAuthEnabled'. I don't know what it wants, just that I have limited time to react. Cannot understand the clearly auto-translated text. Still didn't get what it wants from me when I read it in English. I banned the health check from my logs and said where it can get a response from the service I run. I hoped our friendship ended there. Maybe it did and this is some form of retaliation. The load balancer AWS set up for me now suddenly costs money. And I thought I could just use it to grab the free TLS cert that comes with it... well, the clients pay for the additional costs anyway and I would be surprised if anyone even noticed the price spike. The traffic is minimal but I am surprised it is actually that expensive. I could probably cut the costs in half if I actually had motivation to look through all the settings... Microsoft just cancelled some features of some online service my colleague works with because they want to market an alternative for their BI solution. Did cost him 3 weeks of work at the minimum. The stuff cannot be ported to an on-premise version. Hosting your own server is a lot of work and isn't fun. There is still a lot of work to do if you host on something on such an infrastructure. Somehow the amount of work you have to put into software hasn't decreased. Honestly the main argument for it is that you can give away responsibilities. edit: Just noticed that EBS probably counts as PaaS instead of serverless. I run "stuff" (very simple functions) on Lambda too, but to think it would replace apps like the article suggested seems a bit much. It has its purpose, but nearly everything I have on Lambda is AWS cloud specific. It comes in handy for Alexa integrations for example. I think the container won this fight to be honest.
- 1337shadow 6y ago> Hosting your own server is a lot of work and isn't fun. For me it's easy because i just maintain my ansible roles. It's fun because I get to keep up with OSS and be part of an amazing community. And I get much better hardware for the price.
- liv-io 6y agoThis could have been written by me. And for who ever doesn't have time to maintain roles, there is Ansible Galaxy or tons of roles in GitHub, including mine: https://github.com/liv-io https://github.com/liv-io
- deepstack 6y agoServerless is meant to make bar lower for front-end developer so they don't have to learn the basics about web back-end development and be able to develop apps. I'm very glad if failed! People who don't put time into learning development should not do it.
- kevinmannix 6y agoYour second point broadly makes sense. In fact, it's almost a truism: if you don't put time into learning, you won't have the skills necessary to be able to execute. However, it seems detached from your first point. If one's role is a front-end developer, is it necessary that they know about back-end development? If it is outside their intended job function, why would they need to know about it, if it doesn't get in the way of performing their job? If you are a backend developer, do you need to know about how to host your own infrastructure? Handle your own networking? Chip design? Your logic could be applied to any job function. Each level of the stack benefits from the levels below it being abstracted. We all stand on the shoulders of giants, and we're all much better for it. Overall, I do think it's better that one has a good understanding about the various components one interacts with. Having a grasp of the overall system will come in handy. A curiosity into other parts of the system is beneficial, and likely is one of many indicators of success. However, if job functions can be simplified and superfluous context removed, why should we fault those for taking advantage of that? This issue with "lowering the bar" and being glad that a simplification has "failed" (which, is yet to be determined), reeks to me like gatekeeping. The same logic could be applied to any job role which benefits from simplification. In an extreme example, this logic could be extrapolated to support the notion that anyone who cannot build their own machine from the ground up should never work in a programming position. What height is appropriate for the "bar"?
- k__ 6y agoGatekeeping by randomly drawing the line by learning backend development, aren't we?
- znpy 6y agoI view the serverless, specifically aws lambda, as nice way to hook into the aws system and add some code to handle certain events. Basically, to customize the behavior of "the cloud" where aws falls short (for whatever reason). But developing with "serverless" as base stack? Nope.
- nickcotter 6y agoThat’s what we’ve been using it for, for the most part. Plugging holes in CloudFormation etc.
- RikNieu 6y agoAnd it's so. So. Expensive.
- lumost 6y agoEvery server less design I've seen turns into a complex workflow of distributed functions chained together by a pile of xml. Each example that I've seen could have been replaced with a simple single process job. You should not need to go over the network because you need a process to run for more than 10 minutes. You should be able to check the status of resource creation via for loop. An argument can be made for not needing a server, but I can easily fire off a container in fargate/gks/ecs and get similar benefit.
- microcolonel 6y agoOur approach is to start with a mildly-distributed (among threads within the process) monolith based on future passing, and my impression is that any latency-sensitive operation in a session cluster (that is, all of the sessions who are interacting directly with the same working set of processes and aggregates) can and should be supported by a single node. Rebalancing involves moving the cached aggregate (any blob, like a sqlite database or a JSON file) and/or† catching up the log (sequence of blobs) on the target node. Futures are basically trivial to serialize, so the cost of involving a second node is as little as it could be; and node consolidation can be generalized because each node's dispatcher knows how many times it has accessed a remote process, which means that consensus on who should lead its log can be reached by simply sending it to the node that has the most use for it (with load balancing achieved by nodes simply not bidding for logs when their load factor or total service time is over some threshold, or say the 60th percentile of all the nodes, or whichever of those two is higher). † In some cases it's faster to just catch up the log, rather than sending the aggregate.
- nscalf 6y agoThank you, serverless is the new structure that everyone loves and wants to work in, but no one talks about the downside. I just took over a project that has a serverless architecture. We can't run it locally because the emulator won't run 7/10 of the code, there are memory limit errors that are totally opaque to us since we can't step through and watch it break. We are getting unexplained timing issues that were being worked on via logs in dev. The costs are insane. If we want to say serverless is the future, the future isn't here yet. There are many tools that would need to be built to make serverless viable, and the tools that are built are immature and bad. Not to mention, you're tied to the companies support, so Google was outdated from the LTS for Node for a while. The reality is going serverless means you don't have control over what happens to your code.
- fragmede 6y agoNow, whether or not you, personally, do, is entirely up to you and what you want your career trajectory to go. (Both are equally valid because internally, AWS will always needs ops people that understand computers.) However, a cottage industry of AWS Certified Solutions Architects has already sprung up, and some have been getting lucrative consulting gigs based on knowing the mismash of Amazon names and how best to mash them up. Serverless (specifically AWS Lambda) plays a part in the cloud, but most of your objections are true of the cloud and/or AWS more broadly, and have little to do with, specifically, serverless. (Despite whatever the webdev convention was trying to sell you.) There's a whole world of EC2 instances which are mostly VPSes, to know about that definitively aren't serverless (though there are some really neat cattle-level features that serverless learns from) If the computer is a bicycle for the mind, then the cloud is a car for the programmer's mind. You can definitely build your own stack with your own team that manages to avoids the cloud, but at some point it becomes more than one person can handle. As you scale, there's a points where the cloud does, and does not make sense, but the cloud gets you access to far more resources as a tiny team than would otherwise be available to you.
- FlingBeyond 6y agoI believe one of the main reasons Serverless will never be more than a low-tier niche is the combination of the following: In the end, you are just renting well maintained server farms (well, a specific percentage of operational time of some of the servers in them). There is absolutely no appeal for large technology-based companies do this once they can (the following is the lowest scale example) afford to maintain their own servers, while potentially renting a few offsite backups in other areas of the world (again, this is just the lowest-scale architecture starting at which Serverless is always the worse option). Existing solutions are extremely over-engineered. It can be excused with "officially planning for the use-case where maximum scalability is required", but it's almost certainly a pretense to sell "certifications", aka "explaining our own convoluted badly documented mess". What this actually means is that many SWE's who are good enough to learn to use Serverless effectively, can learn any other framework that allows building distributed systems across server nodes with equal effort. Why would I base my whole business on your vendor locked, sub-optimized dumpster when I can do the same on an infinitely scalable VM networks, that can be ported to literally any vendor who supports $5/mo VMs (or, you know, self hosted if my company is large enough)?
- srram 6y agothe flip side to your statement:smaller companies (like where I am) are not interested in maintaining our own servers and do all the un-differentiated heavy lifting related to maintaining servers. I want my small team to work on things that make us stand out. Running our own servers does not. Vendor lock-in is not a big consideration for us. I increasingly think about cloud vendors like Operating systems. I really dont care which Linux distro we are on. Pick a vendor and run 'natively' on it to go as fast as possible. I'm happy paying AWS for maintaining the servers and getting out of that messy business. There are other concerns about serverless around observability and managability, but vendor lockin and cost is not part of my equation
- gokceozantoptas 6y agoServerless (as far as I can understand) is what we can consider as the early stages of the commoditization of compute. Meaning, similar to electricity or tap water, at some point in our lives we will subscribe to a provider and then just plug and play whatever we want to. It is just we are in the early stages. If you are interested in these kind of stuff, maybe take a look at Wardley Maps: https://medium.com/wardleymaps https://medium.com/wardleymaps