Which Comet solution to choose?

Question

PHP

Good day!

Our project has elements of a social network, billing, lotteries. There was a need to convert it into a single-page web application that would work in real-time mode.

The client must subscribe to such events (channels) as receiving private messages, receiving invitations to friends/team/..., receiving new page content (depending on whether it is open), receiving draw results, etc.

We considered a number of ready-made comet-server solutions, but it turned out to be quite difficult to choose one of them:
1. The APE Server - we did not find projects where it is used and confirmation of the declared load capacity.
2. Dklab_Realplexor. Good documentation and API for PHP. Its reliability is not clear and, again, there are no tests for load resistance; it is also not clear what it has with scalability (it seems to be, but it is not clear how everything is synchronized there)
3. MochiWeb is a powerful solution in the Erlang language. Cons - no one in the Erlang team knows. How justified is the decision?
4. Node.js solutions - it seems to be popular now, and there are javascript programmers.
5. Solutions in Java (glassfish, cometd, ..). It is not clear whether the Java platform should be used as a comet server at all? The core of the project is written in Java, but the comet server must obviously live separately from it.

We have PHP, Javascript and Java developers in our team, so we would like to limit ourselves to these languages, if necessary, finish something or implement something on something.

Answer 1

Dklab_Realplexor,
despite its age, does not lose its relevance. Launched on the server for the 3rd year in a row and works without failures (7k channels, online ~ 200 sessions). Naturally through nginx.

Answer 2

Add HTTP_Push_Module to the list - a module for nginx that adds COMET server functionality to it (http://pushmodule.slact.net/)