Laravel VS Yii2

It was an honor to join Matt Stauffer on the The Business of Laravel podcast to talk about my journey: from building a startup on Laravel, to selling it, and now launching Ghostable — a zero-knowledge environment-management platform for teams that scale.

laravel/laravel - Uses CircleCI

Image compression is crucial in modern web applications where high-performance, responsive user experiences are expected. Efficiently delivering minified images can dramatically reduce bandwidth, accelerate page loads, and improve SEO. Two popular frameworks for backend API development are NestJS (Node.js/TypeScript) and Laravel (PHP), each with robust ecosystems and communities. In this article, we'll explore on-the-fly image compression solutions in NestJS and Laravel, providing practical code examples and an in-depth comparison in terms of performance, code complexity, and developer experience.

My initial idea was to leverage the main application’s queue worker by deploying a queue worker remotely and setting up a secure connection between them using something like Wireguard. Vigilant is written in PHP using the Laravel framework, for queuing it uses Laravel Horizon. This is a queuing system built on top of Redis. All monitoring tasks in Vigilant are executed on this queue, it allows for multiple queues to exist identified by an unique name. Vigilant has queues for uptime, dns, lighthouse etc, this way the different monitors don’t block each other and resources can be managed per type of monitor. To start a queue worker we can run a single command in a container, exactly like the horizon container does now in the current Docker compose setup. So my first try was to deploy a remote Horizon worker that just handles one queue and name it something like uptime:de or uptime:us to specify the location. Horizon already runs in a separate Docker container.

Backend: Node.js, Express.js, Laravel, Firebase

Ready to start your Laravel journey? Head over to laravel.com and dive into the excellent documentation to begin building your next great application!

Laravel is one of the best PHP frameworks I ever tried in my career which works very well with relational databases such MariaDB or PostgreSQL. However recently I had the opportunity to dig into NoSQL databases, specifically into MongoDB that offers amazing features like TTL indexes or embedded documents (aka One to Few relationships).

Frameworks like Laravel simplify development for complex APIs.

We learned this lesson the hard way. Our initial Laravel and Next.js applications worked beautifully for a small team, but as we added more software developers, merge conflicts and build times became productivity killers. We had to refactor both our code architecture and our development processes.

Yii is one of the oldest PHP frameworks, acronym as Yes It Is! It has 14.2k stars and 7k forks on GitHub. It is a fast, secure, and flexible PHP framework for web development, especially for building MVC architecture websites. It is an Object-Oriented PHP framework that requires knowledge of inheritance, polymorphism, etc.

In Yii Framework we have a middleware that will allow us to access our applications without the need to point the web server to the public directory of each template, so we will use the middleware SubFolder::class.

asset-packagist: This is the traditional Yii2 way, here we will add the following to our composer.json.

It is often preferable to manage Yii Assets programmatically. For example, when you use the widget in a page, it will automatically include the required css and javascript files, instead of asking you to manually find these files and include them. And when you upgrade the widget to a new version, it will automatically use the new version of the Yii Assets. In this tutorial, we will describe the powerful Yii Assets management capability provided in Yii Framework .

As we can see in the example above, we have defined the configuration of our packages in files .php (it doesn’t matter if they are YiiFramework packages or not), this allows us to define the configuration of each component in a very simple way to understand.

Now if we want to create an extension, under the code standard used in the Yii Framework v.3 packages, we can use yiisoft/template, provides us the tools necessary for our code to comply with good coding standards they are:

Now we understand how to do any configuration of any YiiFramework package or external, it is not necessary to have a single long and complex configuration file, we can organize it according to the group of configurations and Yii config will do the work for you, as well as the container it applies the definitions for you, with the automatic wiring facility in controllers, which makes it easy to access any container dependency without the need to use static access to it, or depend on the container itself.