2 ms·
Your entire last sentence, except the higher price bit, is just completely utterly false on its face. Serverless is magically simple - and that is DX, magicall
by eagsalazar2 4y ago
Your entire last sentence, except the higher price bit, is just completely utterly false on its face. Serverless is magically simple - and that is DX, magically simple and easy to reason about. Vendor lockin?? Wat? Again utterly wrong and false. The whole point is you are running your code, you define the function bodies, they just get deployed to different serverless hosting services and it is insanely simplifying. Switching from AWS to Netlify to Vercel is not harder than switching under any other approach.
About cost, even though that isn't "completely utterly false" it is misleading. If you are a startup and want to move as fast as possible without incurring tons of tech debt, and don't yet have millions of daily users, you should use serverless functions because the total cost will be relatively small (relative to the insanely high cost of good devs that is -- always optimize for DX and velocity until you actually have scale). If you ever get to the point where serverless is costing you real $$, then refactor then - you've incurred almost no tech debt by waiting and being very very fast prior to that may just be the reason you got to that scale at all.
Go ahead and build a serverless app utilizing a framework that is well aligned with that approach (may I recommend Remix?) and I bet you'll change your tune. My gut tells me you have no firsthand experience because your points are absolutely off base.
- hbrn 4y agoYou're still not addressing my points. What is the big problem that serverless solves? What does it promise and what does it actually deliver? Infinite scalability? It only solves the easiest part of it. Cost reduction? As you seem to admit, generally this is only true at small scale. Security updates? Fair enough, but this has never been the real problem. If you're at a point where security updates are that important you will unlikely leave them in the hands of a third party. My bet is that what you're attributing to the benefits of serverless are not inherent to the serverless itself and are just benefits of infrastructure built around it.
- Existenceblinks 4y agoYeah, somehow "scale" + no server? ("serverless") combined catches VC fishes. I was exited about edge compute but it's been hijacked by these js engine hype that run function on serverless. It becomes indistinguishable between a concept of "compute close to user" and this serverless + js engine thingy. I wouldn't be surprised if large portion of serverless market is javascript. And rust driven wasm. So monoculture right now.