Re:Ask HN: What is your go to stack for REST API?
by TheyCallMeMaxi on Monday November 11, 2019 @09:05AM
(#21504875)
It's just a beefed up EC2. I don't have high traffic so cannot say how well the autoscaling works but apart from that, not much different than putting your app on EC2.
Re:Ask HN: What is your go to stack for REST API?
by TheyCallMeMaxi on Monday November 11, 2019 @09:04AM
(#21504869)
I use Sequelize as my ORM. There are debates around using/not using ORMs but personally I feel weird writing raw SQL in any language except a SQL terminal.
Re:Ask HN: What is your go to stack for REST API?
by monkeydata on Friday November 08, 2019 @08:23AM
(#21481930)
cakePHP on EC2 + postgres on RDS is nice.
toss in some Redis caching and feed it traffic from a load balancer.
you can get a lot done with very little effort.
Re:Ask HN: What is your go to stack for REST API?
by monkeydata on Thursday November 14, 2019 @08:32AM
(#21535194)
yeh, it is quite a bit cheaper. However, heroku is more aggressive in throttling the cheap stuff. I still use it for ci though. AWS simply offers more granular control and a more robust infrastructure. If you dig down into it, you'll see heroku is actually running on AWS.
The stack does not feel outdated at all.
Django REST Framework provides pretty much everything you need for a REST api.
Node + Express + Nginx + Pgsql on Elastic Beanstalk.
Pricing is completely linear with usage (and very low/free for low traffic) and I don’t have to worry about uptime or scalability.
Postgres
Nginx
Digital Ocean