michael_nielsen

Without knowing special needs, whatever you used last time. Rails on Heroku should be fine. Equivalent for Django should be fine.

My sense is that both Rails and Django have become far more complicated than when I used them (mostly, Rails). I don't want to have to study for ages just to get started.

Say more about what the server needs to do and in what usage context? If it’s CRUD-ish stuff and modest scale, I’d stick with whatever you already know.

Pretty basic CRUD app. I wrote some Rails, but so long ago I suspect it's not really relevant any more. I know Python better these days than I know Ruby.

*CRUD* rb: Rails py: Django py: Flask + SQLAlchemy go: Gin + sqlx go: Gin + GORM rs: Tokio + Diesel? *Static website* Nginx + Jekyll https://www.staticgen.com/  shell scripts ;-) *General API* py: Flask go: Gin rb: Sinatra *Platform* CI+CD: Github -> CircleCI -> Docker -> Heroku

If you're just getting back at it, I recommend Flask and MySQL on Digital Ocean / Linode (cheaper) or AWS EC2s. This will save you a lot of headache to deliver somewhat a simple code-base for an idea, without much dependency. There are good Go-framewokrs. and Rails over Django

and if there is have time for learning, I'd check out Elixir and Phoenix. Elixir uses Erlang VM and the code looks very similar to Ruby and Phoenix the framework, very similar to Rails layout. The learning curve is not too steep.