There is swoole so good extension, it is necessary to do long connection to learn Golang?

Use the Apache Bench tool to stress test nginx static pages, Golang HTTP programs, php7+swoole HTTP programs. In the benchmark for 1 million HTTP requests for concurrent 100, the php7+swoole is 75% higher than Nginx/golang performance HTTP://T.CN/R47RPLT
by Rango

So, the problem: in the domestic environment, personal time and Energy limited circumstances, but the long connection is indispensable, what should be the choice?

Reply content:

Use the Apache Bench tool to stress test nginx static pages, Golang HTTP programs, php7+swoole HTTP programs. In the benchmark for 1 million HTTP requests for concurrent 100, the php7+swoole is 75% higher than Nginx/golang performance HTTP://T.CN/R47RPLT
by Rango

So, the problem: in the domestic environment, personal time and Energy limited circumstances, but the long connection is indispensable, what should be the choice?

The Golang + channel is technically more advanced than the Swoole asynchronous callback. But the go language is essentially a statically compiled language, the development efficiency may be between C + + and Java, the difficulty is greater. Php+swoole is simpler to use and easier to implement.

Use what the main or look at your personal situation, 1 company or project requirements with what, 2 realize what kind of function, if is very low-level software or have a lot of intensive operation of code recommended with go, if is to implement some business application recommendations with Php+swoole

Not Daniel.
That depends on the LZ situation, if itself is to engage in PHP, that there is no need to engage in Golang Ah, and Swoole has been a long time to test, PHP7 do not say, do not put Rango the test, try to know how to make a decision.

I still like Golang.

Am I the only one who thinks Golang is a little anti-human?

Author @ Hantian is very clear, I personally think that Php+swoole is currently the main competition is node. js, the use of the same scenario. However, the former has a big advantage, considering the huge amount of PHP in the Web, if your existing project is also built with PHP, using Swoole to write back-end services can be reused a large number of existing modules, which is very important for enterprise development consistency, in theory, only need to maintain a set of foundation on the line.

Wait for Daniel to answer ...

