How to organize backing for a project?

Question

ubuntu

Good afternoon.
After some time, it is planned to start writing a web application, which can be considered similar to Twitter in terms of work and load on it. The start is planned in 3-6 months, so there is time for some training.
Important points - after the start of the application, under favorable circumstances, the load (the number of users and their activity) will grow in peaks, with big jerks, i.e. scalability will need to be built in. The main priority is not speed as such, but stability. A little later, applications for iOS and Android are still planned - this is another don. load.
Now the question is - what is the best way to start writing this? I'm not looking for an answer: "what can you do or what is more convenient", there are specific needs: stability under heavy loads, convenient scaling in breadth (new functionality) and, again, in terms of load. Also, after the launch, other people who will not be familiar with the project will be involved, at this point some NodeJS is deleted from the list.
I'm looking at RoR, but I'm not sure about its stability and performance under heavy loads. What can you advise?

Answer 1

what is $PWD and what do you think it is equal to when the process is started from the cron (I will give a hint that bash profiles are not loaded at this time, and most likely $PWD is empty).
You can also check local mail, see something like
Write the path without a variable.

Answer 2

"on what you can or what is more convenient" is the most correct answer))
php, ruby, c#, even the mentioned node.js are high-level languages, which means that any thing done in one language can be done in another as well language. This is to mention the words "scalability" and "stability" - they are not tied to the language.
If you have no experience, then the first thing to look at is how to organize the work, for example, if there are more specialists in php than in RoR, then you need to take php, since it will be easier to find employees and their salaries will be lower.
Secondly, again, to reduce the budget, if you find a specialist on the .net stack, he will undoubtedly be able to make a scalable and fault-tolerant solution for you, but as a result of his work, it turns out that the licenses are for wines.
If it doesn't matter to you, take the cheaper one)