Hacker News new | past | comments | ask | show | jobs | submit login

I just got into AWS last year and this article does not mention my big mistake that I made. Using RDS for a small scale project instead of EC2.

RDS is super expensive and while you're gaining traction and users you might as well use an EC2 instance.

ElasticBeanstalk seemed like an easy intro to AWS but it steered me into RDS. Of course I've abandoned the whole of ElasticBeanstalk for serverless development lately.

My first intro to AWS was ElasticBeanstalk and serverless seemed too daunting. But now I've been smitten and can't stop thinking serverless.

I feel like serverless in a lot of cases is more expensive than just running a monolith, once you get past the toy example or past the MVP stage.

This is especially true once you factor in all the development overhead, which can ultimately be very expensive to do things correctly with serverless.

Azure have open sourced their serverless engine, so you even have the option of building out your own private serverless infrastructure.

What?! Please excuse my disbelief but I'm an old Linux veteran from the era when we typed M$. ;)

Where can I find this? I assume somewhere in the 1060 repos of https://github.com/Azure

I also assume that even though it's open source, it requires licensed MS Windows servers to run.

Still though, this is just another nail in the coffin of the OLD MS image.

It's MIT, and the host is built on .NET Core, so you can run it on Linux if you want:


Under Satya Nadella the change in Microsoft has been little short of astonishing. A few years ago, I could understand the continued cynicism - but if anything the pace of change has only intensified.

Have you considered using Aurora Serverless? If you're trying to prove market fit, it can be an order of magnitude cheaper than RDS and you don't have to worry about management in EC2.

AWS doesn't recommend Aurora Serverless for production, yet.

Yeah, great for an internal facing app on your company intranet that only needs infrequent access but requires a relational database.

Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact