Personally I kept to node for backend apps and coding. Some python but not too much.
That being said, I'd steer away from learning another language (I see lots of go / ruby / c# posts in the comments) and I'd get yourself accustomed to databases, containerisation, queues, workers etc.
Learn more about back end concepts and patterns for scaling, redundancy, performance and focus less on a specific language. You'll find that if you do want to code for the back end you'll be able to use your JavaScript skills already as an example:
Ruby like apps - use sails.js
Microservice - check moleculer.js
Etc.
There will always be a framework or comparative so dive into concepts more. Databases, orchestration and deployment will be far more reaching for you
Personally I kept to node for backend apps and coding. Some python but not too much.
That being said, I'd steer away from learning another language (I see lots of go / ruby / c# posts in the comments) and I'd get yourself accustomed to databases, containerisation, queues, workers etc.
Learn more about back end concepts and patterns for scaling, redundancy, performance and focus less on a specific language. You'll find that if you do want to code for the back end you'll be able to use your JavaScript skills already as an example:
Ruby like apps - use sails.js
Microservice - check moleculer.js
Etc.
There will always be a framework or comparative so dive into concepts more. Databases, orchestration and deployment will be far more reaching for you
You've got a point there! Really, that's what I am going to focus on aswell - learn some concepts of backend 👍