Hacker News Reader

Comment by fulafel | Hacker News Reader

A slight tangent but are there really signals that indicate AWS Lambda style serverless is becoming a dominant way of making web backends? Especially since the AWS flavour is so developer hostile (APIGW, CloudFormation, highly divergent dev vs deployment setups complicating debugging, etc)

It's fairly painful compared to a normal backend, and it seems like the serverless advocates are on the super high and super low end: big product teams that can justify microservices and the associated high friction, and on the other hand users/use-cases who recoil at keeping a monolithic server turned on all the time even on a wimpy cloud service.

But if you've jumped on the bandwagon, look into Datomic - Ions are the Cloure-native Lambdas there.

View on HN

Yes, I believe so. We've just passed the peak of inflated expectations on the technology hype curve, and the comments on HN reflect this.

But in general - Do people manually deploy MySQL, Postgres, or MariaDB on EC2 servers? No, (most) people use RDS. The servers are still there, but the management is less.

Do people manually deploy RabbitMQ? No, (most) people use SQS.

Cloud providers have been working out of the same playbook for years - provide low-level compute, watch what people build, and create managed services which solve common use cases. Developers love these services, because it's less infrastructure to be on call for, and they can build products faster.

Lambda and Serverless represents the inevitable conclusion of the natural evolution of the cloud. Parts of it are still painful, but undoubtably it's getting easier and more capable.

Sure but RDS, SQS etc make your life simpler and easier, and they work fine with server-ful backend on eg Fargate. I think serverless is still far from providing the same net positive value.

The value of serverless is in commodified operations: once you wrote the code, it’s your favorite cloud provider’s problem to run it. This lets you provide high-availability services without a 24/7 on-call rotation.

RDS and Fargate are not serverless, bc you still have to think about scaling strategies, appropriate network topologies and you might still have to wake up at night to tweak JVM or kernel settings in your containers.

Isn't tihs exactly the other way around in serverless vs container-based backends? Services like Fargate, GCE Cloud Run, App Engine, Heroku etc are good at "just running" your code and keeping it running. Serverless systems like Lambda, Azure Functions, etc need so much plumbing, devops, ci etc overhead around them that they are full time work for someone in a project.

I'd strongly disagree with that assessment after building on serverless platforms full time for 9 months. I'll never go back to a server-full backend.

Interesting. Are you thinking about this vs a monolithic back end or microservices back end? (Monolithic for me).

Reply on news.ycombinator.com