3 ms·
Anything whose main value proposition is about “ability to scale” will likely trade off your “ability to be agile & survive”. That’s rarely a good trade off. I
by k__ 7y ago
Anything whose main value proposition is about “ability to scale” will likely trade off your “ability to be agile & survive”. That’s rarely a good trade off.
Interesting that he sees micromanaging infra on AWS as more agile than using managed services.
Also, serverless systems don't cost you money when you(r customers) don't use them, so that's a huge plus on survival.
Finally, code you write is always a liability, if you got a good architecture (hexagonal, etc.) you can just swap out one service that saved you time in the past with another service that will save you time in the future.
- awinder 7y agoYeah for launching startup level traffic I totally agree, lambda feels like the right arch at the right cost. Also it will engrain setups that, like you said, you can swap out. You’ll need an alb / api gateway, you’ll need to get logs flowing through cloudwatch or some other non-host logging mechanisms. Transferring onto these kinds of architectures from not-these-architectures has been a royal pain and a time drain in my experience.
- gtirloni 7y agoYeah, kind of made me cringe a bit (considering his experience).
- freehunter 7y ago>serverless systems don't cost you money when you(r customers) don't use them All the horror stories I see surrounding huge surprise Lambda bills always bring me back to this point. If I have to pay $5/mo for a server I only use for two hours once every few months, that's something that should go on Lambda. If it's something that I'm using constantly, all day every day, a server will be cheaper. If I only use my car once every few weeks, Uber makes a lot of sense. If I use it every day back and forth to work and the grocery store, Uber's gonna be a lot more expensive. Lambda is for small tasks that don't execute often. And using it right can save startups gobsmackingly large amounts of money.
- k__ 7y agoYes, it comes all down to risk assessment. Maybe using serverless technology is too hard for your corp, because you don't have the skills, so it could lead to problems in the future (surprise Lambda bills). But it could also be that your competitors get a huge advantage by investing in the serverless paradigm and run you away in the future. To me that Twitter thread sounded too much like a guy who invested in some tech over the last 11 years and now tries to convince potential customers of him to use the tech he knows about. He could be right, he could be wrong. I don't know. I started back-end development with serverless, so I'm biased in the other direction, haha.