Book Image

High Performance with Laravel Octane

By : Roberto Butti
5 (2)
Book Image

High Performance with Laravel Octane

5 (2)
By: Roberto Butti

Overview of this book

Laravel Octane is a very powerful component in the Laravel ecosystem that can help you achieve remarkable app performance. With Laravel Octane, you will find tools (queues, cache, and tables) that facilitate a new asynchronous approach for improving application performance. This book highlights how Laravel Octane works, what steps to take in designing an application from the start, what tools you have at your disposal, and how to set up production environments. It provides complete coverage of the strategies, tools, and best practices to make your apps scalable and performant. This is especially important as optimization is usually the overlooked part in the application development lifecycle. You will explore the asynchronous approach in Laravel and be able to release high-performing applications that have a positive impact on the end-user experience. By the end of this book, you will find yourself designing, developing, and releasing high-performance applications.
Table of Contents (14 chapters)
Part 1: The Architecture
Part 2: The Application Server
Part 3: Laravel Octane – a Complete Tour
Part 4: Speeding Up

Prepping a Laravel application for production

Now, we will focus on Laravel-specific configurations for the production environment. We will see how to install production PHP/Laravel packages, avoiding installing packages for development and debugging. We will see how to optimize cache configurations, routing settings, and view optimization. Finally, we will see how to inhibit debugging options. Debugging options are very useful in development, but can slow down the execution of the Laravel application in production.

Installing the packages for production

In the composer.json file, two types of packages are listed: require defines the packages for running the application in a production environment, and require-dev defines the packages for running the application in a development environment.

By default, composer installs all the packages from both lists.

If you only want to install the packages from the require list (production), you can use the –-no-dev option while...