Rapid backend deployment: which technology to choose?

Question

Ruby on Rails

Hello.
I haven't worked on a "hardcore" backend for a long time (not CMS: s ala WP, etc.) ...
At one time, in the year 2011-2012, I used Ruby on Rails and, in fact, something was deposited in my head, but I'm afraid that since the 3rd version has gone through a lot of changes ... How critical are they for updating their old knowledge?
Now I'm competing on the front with angular ... And it seems like seasoned fronts could beat me with their feet if I said that I was faced with the choice of RoR vs Node.js ...
Node.js is quite popular now ... But here's what the threshold for entering it, from zero to production?
The essence of my application: for car mechanics something (mystery :D ), mysql database (because there will be a couple of export tables, something like tekd * k), everything is ok with the front ... But what would you advise with the backend?
Upgrade your “brain” to rails 4.2 (which will also be time-consuming) or start “nodding” from scratch (which will also take time, but it seems like .js, maybe not everything is so hard?).
Nothing supernatural: REST, JSON, CRUD.
What do you advise, experts? Throw a couple of ideas to think about ...
Thank you

Answer 1

If you were engaged in rails 3.2+ on ruby ​​1.9+, then you will not feel big problems when switching to 4.2. As a last resort, you may not use some of the latest features / conveniences.
A relational CRUD node is hardly a good option.
If you don’t expect anything supernatural from the backend, as an option - look at any (m)BaaS - parse.com, firebase, databoom ...

Answer 2

By the will of fate, I was forced to write a small module in Node. The task is not trivial, working with FabricJs, generating an image from canvas and putting it on AWS S3.
This could be done either in the browser + RoR or RoR + Node, chose the latter. While you are only reading articles about Node, everything is perfect, it works great, but there is one big problem, these are memory leaks. If the pros know the subtleties, then yes, it’s possible to somehow screw it up in production. If not, then this hemorrhagic will start to kill the server and the difficulties will turn out not in the field of JS as a language, but in the field of subtle points, as I described above. Async and other troubles will go further there, when you think that the process is 100% debugged and it is so in RoR, but in Node the load is of great importance and under load the processes begin to behave differently and what used to work breaks. Again, everything is solved for the pros, as for the pros in any language. But if there is no specific knowledge of troubles with Node, then this is only by experience, sweat and blood. I found a way to get away from these problems on Node, but in my task it was possible and stayed on it, otherwise, I would have to refuse. But in general, for me personally, Node is rather a toy for small applications, I would not dare to write on it in production, well, if you just take some kind of ready-made framework, of which there are 5-6 pieces on the node, for example, Meteor, but this is also, that’s all it’s good when you read and use it on small tasks, as it will be in the sale, it’s a big mystery.

Answer 3

When I needed to deploy a backend without backend knowledge, I chose SailsJs
Nothing complicated, we generate the backbone, models, controllers and you're done.

Answer 4

see Heroku, Docker, Dokku

Answer 5

The fastest way to deploy the backend on heroku