No post body was provided.
Ask HN: What web application server back end would you use for a new project?
1–9 of 9 posts
Re: Ask HN: What web application server back end would you use for a new project?
#2ASP.NET Core, it's a great ecosystem with great tooling, and C# is fantastic language to work with. I develop on Windows, deploy to Linux with Docker, docs are great too.
Re: Ask HN: What web application server back end would you use for a new project?
#3I've been wanting to try nhost, but if it's something you'd want to put in prod fairly quickly, I'd go with Firebase.
Re: Ask HN: What web application server back end would you use for a new project?
#4[deleted]
Re: Ask HN: What web application server back end would you use for a new project?
#5I want to try postgrest.
Re: Ask HN: What web application server back end would you use for a new project?
#6Rails.
Re: Ask HN: What web application server back end would you use for a new project?
#7This strongly depends on the purpose...
How is it sized?
Can it get bigger?
Is it realtime?
Is it Web / App / Other frontend?
What backend languages / tech is supported?
SignalR (C#)
Flask (Python)
Gorilla (Golang)
Revel (Golang)
API Platform (PHP)
Hapi (js)
Express (js)
Actix-web (rust)Re: Ask HN: What web application server back end would you use for a new project?
#8I've been really happy with express (Node). It has scaled really well for my company.
Currently processing almost 200 million requests a month on a cheap $25/mo heroku dyno.
Re: Ask HN: What web application server back end would you use for a new project?
#9I've been really happy with express (Node). It has scaled really well for my company. Currently processing almost 200 million requests a month on a cheap $25/mo heroku dyno.
Note that this means 77 requests per second, which is not impressive at all.
200000000/(30x24x60x60) ~= 77.16