Programming Phoenix

Concurrent

If you’re using an object-oriented web framework, chances are that you’re watching the evolution of multicore architectures anxiously. You probably already know that the existing imperative models won’t scale to handle the types of concurrency we’ll need to run on hardware with thousands of cores. The problem is that languages like Java and C# place the burden of managing concurrency squarely on the shoulders of the programmer. Languages like PHP and Ruby make threading difficult to the point where many developers try to support only one web connection per operating-system process, or some structure that is marginally better. In fact, many people that come to Phoenix find us precisely because concurrency is so easy.

Consider PhoenixDelayedJob ...