We did, we had a play with Swoole and Phalcon when we were in the RFC stage of our project. We found Phalcon to be a bit too opinionated in how to do things, a

We did, we had a play with Swoole and Phalcon when we were in the RFC stage of our project. We found Phalcon to be a bit too opinionated in how to do things, and we fell in love with how Swoole has implemented Coroutines and (practically) free context switching between long running asynchronous processes and short running network requests. Looking back, I do actually wish we had chosen Phalcon (the documentation is a lot better than Swoole's, which is lacklustre to say the least, and occasionally intersperses random characters in Simplified Chinese halfway through sentences), but we've been happy with Swoole's Table implementation which allows us to share memory between network request Coroutines and hit the Redis cache a whole lot less.