How to write a client-server with 10,000+ online and 36,000,000 requests per hour?

Question

PHP

Hello!
A project is being developed for mobile on phonegap ( android, ios, wp8 )
In the application, a service that works foreground. In this case, a large number of requests to the server are made.
Select, update, insert queries.
Since people leave the service at night and do not turn it off during the day, there is a rather large load on the server.
Requests from the application are sent via AJAX and the server is Apache2 and mysql.
The data exchange format is json.
What will be the easiest and fastest solution? Maybe it's better to make a permanent connection through websockets & Node? Or is there nginx + php-fpm?

Answer 1

at first reach ©
the Apache maintains such loadings if cho. and you can and should attach a balancer, but then.
this is a blank question. no information about how much information should be transmitted at any interval, etc.
I try to do it somehow, and then you will already change and modify

Answer 2

"On what" is not the right question.
There is nothing terrible for the technologies you use in such a load.
PHP and Facebook uses. MySQL and mail.ru uses.
It is necessary to plan the architecture correctly.
The correct use of caching in RAM reduces the load very cool
habrahabr.ru/search/?q=Tarantool

Answer 3

10k rps is not bad. 1 server in production will not stand it. There is even a known problem with 10k connections.
The main task in designing such a system is synchronization and load distribution.
Easy and fast - these are not the words that are applicable here)) reliable and productive - closer to the body.
Websockets are not compressed, there may be problems with traffic.
Generally. It is impossible to answer your question without a detailed brief (as I understand it, it still needs to be compiled).