Recommend on what to make a backend?

Question

Perl

What to do backend?
The application is similar in structure to a chat with rooms, but not user phrases are sent, but service information.
Requests from customers are expected, sometimes in quite large numbers. Queries can be relatively time consuming. In principle, a delay in server response of 1-2 seconds will not create a problem. But more - I would not want to.
Options:
- PHP. The downside is that after each execution the script is killed, but I would like to store some information from session to session. For example, authorization data. You can store them on the database server, but then each script run also means a call to the database server. It seems that there are some methods for storing static data, but, as I understand it, this is a kind of dancing with a tambourine.
- node.js, Confused by its single threading. There is a considerable risk that a new request will arrive before the processing of the old one is completed. How to debug it - xs.
- python. Minuses?
- perl. Minuses?
- maybe something else?
Performance matters
UPD: the question is "what to do", not "whom to contact". "Find someone to do it" options don't work

Answer 1

www.rabbitmq.com

Answer 2

In each of these languages, you can make a quick implementation.
Judging by this:
the question is more in the plane of programming experience than the choice of a particular language.
But even without this, it is usually most effective to write in what the team is best at.

Answer 3

I'm not saying what should be done in php, but all the disadvantages described are not adequate.
one . Authorization data in the session, and the session is not necessarily in the database.
2. The database is not a php attribute. In any case, you will have a database and there will be queries to it.
3. There are sockets and chats on them are done more often.
PS: According to such a description (2 paragraphs), it is not correct to give advice on choosing a tool. But as a rule, you can do it on each of the above technologies and you should choose what you know.

Answer 4

- node.js, Confused by its single threading. There is a considerable risk that a new request will arrive before the processing of the old one is completed. How to debug it - xs.

So the platform is responsible for this. New requests simply stand in a queue (well, of course, if they are not interrupted by a timeout client or reverse proxy).

Answer 5

> store on the database server, but then each script run also means accessing the database server,
you can use memcached

Answer 6

Try the PHP + CppComet bundle , in which CppComet will serve connections via web sockets, and the php backend will serve regular http requests and execute the business logic of your application.
The issue with authorization will be solved simply because the CppComet api provides an authorization mechanism
. By itself, CppComet is a multi-threaded server in C ++, and api calls can be made from any backend.

Answer 7

Everything is too superficial, the most correct option is to find a competent project manager (with a lot of development experience) and he will already be able to decide on what to write your project and entrust the development team to him, so that he recruits and manages, otherwise shit will turn out.
And you need to trust this person and then the project will really work out.