Building functional listener with best practices (#1095)

12. mart 2026. 04:21:11 Alice Smith

Concurrency Patterns in PHP

PHP's traditional request-per-process model is simple but limiting. Modern PHP offers several concurrency approaches.

Fork-Based Parallelism

Using pcntl_fork(), a parent process creates child processes that inherit its full state via OS copy-on-write:

$futures = [];
foreach ($chunks as $chunk) {
    $futures[] = run(function () use ($chunk) {
        return processChunk($chunk);
    });
}

$results = array_map(fn ($f) => $f->value(), $futures);

Advantages: Full state inheritance, true parallelism, no serialization overhead for captured variables.

Challenges: Connection management (database, Redis, HTTP clients must be reset in child processes), memory overhead per process.

Async I/O

For I/O-bound workloads, async libraries like ReactPHP or AMPHP multiplex operations on a single thread:

$promises = [];
foreach ($urls as $url) {
    $promises[] = $httpClient->request('GET', $url);
}
$responses = await(all($promises));

Advantages: Low memory footprint, excellent for HTTP calls and database queries.

Challenges: Callback complexity, limited CPU parallelism, ecosystem compatibility.

Choosing the Right Model

| Workload | Best Approach | |----------|--------------| | CPU-bound computation | Fork (pcntl) | | Many HTTP API calls | Async I/O | | Mixed CPU + I/O | Fork with async per child | | Real-time streaming | Event loop (ReactPHP) |

concurrency incididunt lorem refactoring

Prijavi me da objaviš komentar

5 komentara

John Doe komentar objavljen 12. 3. 2026. 17:25

Nunc viverra elit ac laoreet suscipit. Vae humani generis. Sunt accentores vitare salvus flavum parses. Pellentesque vitae velit ex. Teres talis saepe tractare de camerarius flavum sensorem. Morbi tempus commodo mattis. Diatrias tolerare tanquam noster caesium. Ubi est barbatus nix. Aliquam sodales odio id eleifend tristique. In hac habitasse platea dictumst. Pellentesque et sapien pulvinar consectetur. Silva de secundus galatae demitto quadra.

Bob Johnson komentar objavljen 12. 3. 2026. 17:24

Eros diam egestas libero eu vulputate risus. Potus sensim ad ferox abnoba. Nulla porta lobortis ligula vel egestas. Diatrias tolerare tanquam noster caesium. Era brevis ratione est. Eposs sunt solems de superbus fortis. Ut suscipit posuere justo at vulputate. Sunt seculaes transferre talis camerarius fluctuies. Lorem ipsum dolor sit amet consectetur adipiscing elit.

Grace Wilson komentar objavljen 12. 3. 2026. 17:23

Sunt accentores vitare salvus flavum parses. Lorem ipsum dolor sit amet consectetur adipiscing elit. Ubi est barbatus nix. Sunt torquises imitari velox mirabilis medicinaes. Pellentesque et sapien pulvinar consectetur. Mauris dapibus risus quis suscipit vulputate.

Alice Smith komentar objavljen 12. 3. 2026. 17:22

Diatrias tolerare tanquam noster caesium. Lorem ipsum dolor sit amet consectetur adipiscing elit. Silva de secundus galatae demitto quadra. Teres talis saepe tractare de camerarius flavum sensorem. Ut eleifend mauris et risus ultrices egestas. Pellentesque et sapien pulvinar consectetur. In hac habitasse platea dictumst.

Bob Johnson komentar objavljen 12. 3. 2026. 17:21

Potus sensim ad ferox abnoba. Ubi est audax amicitia. Diatrias tolerare tanquam noster caesium. Bassus fatalis classiss virtualiter transferre de flavum. Nunc viverra elit ac laoreet suscipit. Ut eleifend mauris et risus ultrices egestas. Sunt accentores vitare salvus flavum parses. Eros diam egestas libero eu vulputate risus. Morbi tempus commodo mattis. Sunt seculaes transferre talis camerarius fluctuies.

Ova demo aplikacija je napravljena u radnom okviru Symfony kao ilustracija preporučenog načina razvoja Symfony aplikacija.

Za više informacija pogledajte Symfony dokumentaciju.

Kliknite na dugme ispod da biste videli izvorni kod kontrolera i šablona korišćenih za prikaz ove stranice.

src/Controller/BlogController.php at line 272

/**
 * NOTE: when the controller argument is a Doctrine entity, Symfony makes an
 * automatic database query to fetch it based on the value of the route parameters.
 * The '{slug:post}' configuration tells Symfony to use the 'slug' route
 * parameter in the database query that fetches the entity of the $post argument.
 * This is mostly useful when the route has multiple parameters and the controller
 * also has multiple arguments.
 * See https://symfony.com/doc/current/doctrine.html#automatically-fetching-objects-entityvalueresolver.
 */
#[Route('/posts/{slug:post}', name: 'blog_post', requirements: ['slug' => Requirement::ASCII_SLUG], methods: ['GET'])]
public function postShow(Post $post): Response
{
    // Symfony's 'dump()' function is an improved version of PHP's 'var_dump()' but
    // it's not available in the 'prod' environment to prevent leaking sensitive information.
    // It can be used both in PHP files and Twig templates, but it requires to
    // have enabled the DebugBundle. Uncomment the following line to see it in action:
    //
    // dump($post, $this->getUser(), new \DateTime());
    //
    // The result will be displayed either in the Symfony Profiler or in the stream output.
    // See https://symfony.com/doc/current/profiler.html
    // See https://symfony.com/doc/current/templates.html#the-dump-twig-utilities
    //
    // You can also leverage Symfony's 'dd()' function that dumps and
    // stops the execution

    return $this->render('blog/post_show.html.twig', ['post' => $post]);
}

templates/blog/post_show.html.twig at line 1

RSS članaka na blogu