Vapor now allows for individual queue concurrency settings, enabling developers to specify the number of concurrent workers for each queue separately.

Developers can configure their Laravel Vapor environment to utilize multiple queues for their application. 

id: 12345
name: my-project
environments:
    production:
    queue-concurrency: 100
    queues:
        - default
        - invoices
        - mail
When deploying a configuration similar to the example above, Laravel Vapor creates three SQS queues (if they don't exist) and sets up an event mapping between each queue and a Lambda function to process the jobs. Although all queues use the same Lambda function to process jobs, which is generally efficient since Lambda picks up jobs almost instantly, this also means that all queues share the function's concurrency configuration. This configuration is either explicitly set using the queue-concurrency option in the vapor.yml file or uses the overall account concurrency by default. Previously, a busy queue consuming most of the allowed concurrency could cause other queues and even HTTP requests to be throttled by AWS. However, a recent update to Lambda and SQS has addressed this issue, allowing developers to set the concurrency of individual queues to prevent throttling. 

id: 12345
name: my-project
environments:
    production:
    queue-concurrency: 100
    queues:
        - default: 80
        - invoices: 10
        - mail: 10
The above configuration sets the overall function concurrency of the queues to 100 and allocates the available concurrency among the three queues according to our desired distribution. What is happening behind the scenes? For the default queue, AWS sets a maximum concurrency of 80 during the provisioning process. If the queue processes enough jobs to reach the concurrency limit, the Lambda function stops reading from the queue until more capacity is available. This prevents throttling and avoids triggering the redrive policy, allowing SQS to avoid making decisions about throttled jobs. Laravel Vapor simplifies configuring individual queue concurrency. For instance, imagine a scenario where a video processing queue is likely to consume almost all of Lambda's maximum invocation time of 15 minutes. To prevent this queue from monopolizing resources, we can create a default queue with no concurrency limit, ensuring that jobs are processed quickly without hitting the concurrency limit. We can also create a videos queue with a concurrency limit of 2, which takes longer to process jobs but prevents the rest of the environment from being affected. 

id: 12345
name: my-project
environments:
    production:
    queue-concurrency: 100
    queues:
        - default
        - video: 2
Deploying the configuration above will do just that. It's that simple! We at Vapor are committed to crafting the best serverless PHP experience, and we hope you agree this feature is another step in the right direction. We look forward to and welcome any feedback you may have.

Comments

Post a Comment

Popular posts from this blog

Laravel Model

Laravel is a popular PHP framework that makes it easy to build web applications using a modern and expressive syntax. One of the most powerful features of Laravel is its elegant and intuitive approach to working with databases through an Object-Relational Mapping (ORM) system called Eloquent. Eloquent allows developers to interact with databases using PHP objects instead of raw SQL queries, which simplifies the process of creating, reading, updating, and deleting records in a database. At the heart of Eloquent is the Model, which represents a database table as an object-oriented entity. A Model is a PHP class that extends the Illuminate\Database\Eloquent\Model class and defines the structure and behavior of a database table. Each Model contains properties that represent the table's columns, and methods that define relationships between tables or perform data manipulation operations. Creating a Model is easy. You can generate a new Model using the Artisan command-line tool: php a...
Read more

Laravel Artisan: The Command-Line Interface for Your Laravel Application

If you're a Laravel developer, you're probably already familiar with the powerful command-line interface that comes with the framework: Artisan. Laravel Artisan is a powerful set of CLI tools that can help you with everything from generating boilerplate code to database migrations and even job scheduling. In this blog post, we'll dive into some of the most useful Artisan commands and explore how they can make your Laravel development experience more productive and efficient. Getting Started with Artisan To get started with Artisan, simply open up your terminal and navigate to the root directory of your Laravel application. From there, you can run any Artisan command by typing php artisan [command] . The first command you should try is list. This will show you a list of all available Artisan commands. You can also run php artisan help [command] to get more information about a specific command. Generating Boilerplate Code One of the most common tasks in any Laravel ...
Read more

Laravel Facades

Laravel is a popular PHP framework that has gained a lot of popularity in recent years. One of the features that make Laravel so popular is its Facades. In this blog post, we will explore what Laravel Facades are, how they work, and why they are useful. What are Laravel Facades? Laravel Facades provide a static interface to classes that are available in the application's service container. In simple terms, Facades allow you to access Laravel services without having to instantiate them or use dependency injection. Facades provide a simple, easy-to-use syntax for accessing Laravel services. For example, instead of instantiating the  Illuminate\Mail\Mailer  class, you can use the  Mail  facade to send an email: Mail :: to ( $user )-> send ( new OrderShipped ( $order )); Behind the scenes, Laravel resolves the  Illuminate\Mail\Mailer  class from the service container and calls the  to  and  send  methods on it. How do Laravel Facades wor...
Read more