The task is to implement the parameterized impact (that is not static, but there are a finite number of configurations that are in printsepe, it is possible to cache) page embed player for users. Expect serious load — more than 5 million unique queries a day.
In General, always enough chords php + nginx + apc cache + memcache. As storage mongodb or redis. But the brain crave perversion, and it has long stuck to the idea of using erlang for web applications.
The question is, is it worth it? And if so, where better to watch.
5 million hits per day is not such a big number for a project in php. So if you are not sure what profit will the use of erlang, the reason for its use can be only one "the brain wants perversions". If it is also in the conditions of the already working project is done, you should add one point to the problems of "adventures on the fifth point".
Personally, I'm in php-first project for erlang see only one niche — the retention of long-standing connections with the clients (web chat). If the project is jabber. Or if the project has a queue which can be good gash in RabbitMQ. In these cases it is very good shows itself.
nathanael.Weber answered on October 8th 19 at 03:15