Answer the question
In order to leave comments, you need to log in
Using Erlang for the Web?
The task is to implement the return of a parameterized (that is, not static, but there is a finite number of configurations that, in principle, can be cached) embed player pages for users. A serious load is expected - more than 5 million+ unique requests per day.
In general, the php + nginx + apc cache + memcache bundle is always enough. As a mongodb or redis store. But the brain craves perversions, and the idea of using erlang for web applications has long been in it.
The question is, is it worth it? And if so, where is the best place to look?
So far I'm focusing on chicagoboss.
Answer the question
In order to leave comments, you need to log in
You can also look at nitrogenproject.com/ .
>The question is, is it worth it?
Only if the brain craves perversions and the content is well cached.
For your task, the Boss will be redundant. Misultin works well . Benchmark .
5 million hits per day is not such a big number for a php project. Therefore, if it is not known exactly what profit the use of erlang will give, then the reason for using it can be only one “the brain wants perversions”. If this is also done in the conditions of an already working project, then it is worth adding one point to the problems of “adventure to the fifth point”.
Personally, I see only one niche in the php project for erlang - keeping constant connections with clients (web chat). If the project has jabber. Or if the project has queues that can be well filed in RabbitMQ. In these cases, it performs very well.
Here are examples of Erlang sites on Nitrogen compatible N2O framework:
skyline.synrc.com
synrc.com:8080/static/app/index.htm
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question