I consider node.js + sockjs or tornado + sockjs.But I understand the question very badly.Before it was necessary to write only on C + php + javascript + mysql + html + css.In general, my level is not particularly high, but I am learning(At the moment, I liked python - I am studying)
As a matter of fact, first of all I want to initially choose an asynchronous server so that in the future I don’t have to choose another one.And start learning work with him.There are so many things on the Internet that I'm just confused.
They say that node.js falls periodically.but also found information that this is due to server idleness - you can increase the length of the timeout, in case the server is idle longer than usual.I also found out that with node math everything is very bad.In this regard, the question to which I did not find the answer on the Internet: Is it possible to fasten something to the node in order to work with mathematics as well.
I was also interested in tornado, but only because I most often mentioned him.
Interestingly, all of this works faster, more stable?
Generally speaking, I will be glad to hear completely different solutions.And in order not to take precious time from psychics, I will describe what I would like to achieve using selected servers + libraries:
The plans in addition to learning, of course, have a project idea: A site builder with the ability to transfer instant messages between users(for short).In this case, mathematical calculations are also of interest because of my professional specialty.I want to be able to write mathematical services and fasten them to the project, or just write a mat.services and do not fasten - not so important.+ I would like to have the opportunity to work with libraries for processing 3D and m p - just in case,"but what if you are interested in sometime?" I repeat that I don’t want to change the decision in the future.I plan to grow and learn mostly on the web.
Sorry for the sheet and thank you in advance for your help and answers.

1 Answers 1

All others are ..
  • Based on what is written. The best option is Misultin. But you have advised Cowboy. You can ask why? – Bouncin'45 Aug 9 '16 at 14:11
  • Misultin is not supported anymore. – Cautious31 Aug 9 '16 at 14:34
  • >What is the number of desired connections from clients and how much server was able to pull?
    yes. you can see what limits in service from the servers. You can take a thread b, there is even better
    – Cautious31 Aug 9 '16 at 14:36
  • Cautious31: Thank you very much – Bouncin'45 Aug 9 '16 at 14:55
  • Cautious31: Began to study Erlang. Mostly very unusual language.
    >you can take a thread b, there is even better.
    What do you mean? I couldn’t find anything for cowboy requests in c language, cowboy si and mn. However, I came across such a thing https://github.com/brianhicks/cowboy.
    The terrible code of the test server on cowboy (erlang) + sockjs https://github.com/sockjs/sockjs-erlang/blob/maste .. .
    Usual js code under node https://github.com/sockjs/sockjs-node/blob/master/...

    Are there any other options? Or will just learning Erlang give you the opportunity to have a good fast and stable server?
    – Bouncin'45 Aug 9 '16 at 18:06
  • In general, I would not like to switch to Erlang. It would be nice to have something compatible with Python. Since I already began to study it – Bouncin'45 Aug 9 '16 at 18:47
  • >What do you mean? I couldn’t find anything by cowboy requests c language, cowboy si and mn. However, I came across here
    I meant what thread s nginx server type and the lua cheek for it :) if you write.

    >The scary code of the test server on cowboy (erlang) + sockjs
    do not worry if it's not Python - it's not scary yet, just not familiar.

    >Are there any other options? Or just learning Erlang will give the opportunity to have a good fast and stable server?
    Yes, use what you want. just know about the application area.
    Study C and the gate of the highway will open for you :)
    – Cautious31 Aug 9 '16 at 19:29
  • Cautious31: Well, I’m more accustomed to si) For the year was studied in high school. Although I'm still not a programmer – Bouncin'45 Aug 9 '16 at 19:52
  • Cautious31: I'm completely confused: (here centminmod.com/siegebenchmarks/2013/020313 write that node copes with the load better than nginx, but the article above says that cowboy is clearly more stable and faster than node. But you say that the best option is to use the C server like nginx.
    Please explain what I don't understand?
    – Bouncin'45 Aug 9 '16 at 20:35
  • Nginx is the fastest http server. Inside, it processes all threads asynchronously using the epool library (well, inside it, it is already done sequentially on each core, because it can digest 1 operation at a time). Apache uses the usual processes from the operating system, so has the overhead of creating/killing such a process. And this is a very difficult operation for the OS. Therefore, everyone prefers nginx to apache. And Apache is used only as a server for heavy logic, because it has true parallelization. While nginx is designed to quickly give a quick response.
    Knowledgeable people will correct me, but I think it doesn't matter to you at this stage.
    Just look at what will be more useful to you in the future.
    – Cautious31 Aug 9 '16 at 20:37
  • Cautious31: Good. Thank you very much. You helped a lot – Bouncin'45 Aug 9 '16 at 20:41