I would still prefer to use ActiveRecord and a whole lot of other pieces of Rails for an app that's purely an API backend. Ex: http://edgeguides.rubyonrails.or

I would still prefer to use ActiveRecord and a whole lot of other pieces of Rails for an app that's purely an API backend. Ex: http://edgeguides.rubyonrails.org/api_app.html http://edgeguides.rubyonrails.org/api_app.html On the Python side of things, I'd use tools like SQLAlchemy and a few other packages. Every web application I've built can still be efficiently modeled with a relational database. An ORM that lets me model things quickly and allows me to avoid shooting myself in the foot by easily monitoring raw queries is going to win in my book when it comes to picking a tech stack to work with. The major ecosystem problem is that no one can just wake up and be like... I'm going to spend the next year making a Rust version of Rails. These features and ideas need to come from real life use cases, that's really 99% of Rails' success. It can be done in any language of course, but you're 10 years behind the curve.