If you were going to set up a server-backed website, what language/library/framework would you use these days (& why)? It's been several millennia since I looked at Rails, Sinatra, Django etc...
Perhaps a better question is: how easy would it be to move? My guess is that it's very likely there will be sharp peaks in useage (certainly > 10^5, maybe 10^6 pageviews in a day). But beyond that, no surety.
-
-
It's easy to scale Heroku up/down and they prorate to the second If you have to move, you're not locked in. Nothing proprietary that you depend on. I have not actually tried this though
- End of conversation
New conversation -
-
-
If you bake your app with Docker it's trivial to move off of Heroku. You can bake Docker images with, say, CircleCI. Or just use Heroku buildpacks (i.e. they compile the project for you) and then pay the small migration cost when you want to move off of the platform.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Nginx, Hugo, Gin can easily serve thousands of requests per second. Rails and Django can serve that if you put a simple cache in front of it. Note that Heroku bandwidth is free which is a huge benefit for hobby projects.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
If you want a more DIY-feeling managed solution, AWS' Elastic Beanstalk will let you use very cheap instances (t2.micro) and scale them up and down automatically according to traffic magnitude or CPU usage.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Heroku starts at 7USD/mo and the VMs are powerful enough to serve many websites just fine, in my experience. They are even fine for CPU-intensive APIs (such as for serving predictions).
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.