What is the principle to choose technology for the backend?

Question

Programming

I have a task that needs to be implemented in the long term.
Software for housing and communal services. Accordingly, intensive work with the database.
Because I am not a system architect, I find it difficult how technologies are selected here.
You can randomly poke a finger at Ruby or some of the server-side javascript frameworks that are fashionable today (which is not a fact of what will happen tomorrow, and you will have to leave it as it is, or refactor). Or you can stand up for the good old PHP, because apparently it will not go anywhere, it is easier with the server, and the man-hours for maintenance are cheaper.
But how do I choose the right technology for my project?
Maybe there is an approximate algorithm, or do YOU ​​already have your own algorithm?

Answer 1

There is no algorithm in most cases. You take either what you know best, or what you want to work with and are more or less sure of it.

Answer 2

The choice of technologies is the result of analysis and research on those. task.
For example, projects tied to the event model will probably be easy to write and maintain on a node. Projects tied to ms - in c#. Projects that will develop very dynamically - it will probably be the easiest to maintain in puff, etc.
Not the last issue is popularity, for example, you decided to write in Erlang, then your engineer quit and it turned out that he is the only specialist in this language in your city.

Answer 3

django
Initial release July 21, 2005; 11 years ago
I take the framework from which there were no problems and pain

Answer 4

Or you can stand up for the good old PHP, because apparently it will not go anywhere, it is easier with the server, and the man-hours for maintenance are cheaper.

Yes. Not that he somehow ran ahead of the rest, but it will be cheaper. Both in development and maintenance.