laravel-actions VS adr

Let's install laravel actions package to help us with crafting actions that we can use anywhere

First, this is an excellent question. But to answer it, we need to define some terms. Do you mean "action" as in ADR, where the action class is what would have been a controller action method (aka "single-action controller")? Or do you mean "action" as the Laravel folks often use it, a la https://laravelactions.com/ ?

I could have accomplished the same result with a simple command. But as I mentioned: "For this project, I decided to experiment with Laravel Actions. It is not required but seems like the right tool for the job.". There is definitely more value in the concept than explained in my brief example.

Good package for making Actions: https://github.com/lorisleiva/laravel-actions

https://laravelactions.com/ https://laravel.com/docs/9.x/queues#adding-jobs-to-batches

As mentioned before, Jetstream has the concept of Actions. This is a "pattern" that has emerged in the Laravel community in the last few years. There is also a nice package to make working with Actions easier: Laravel Actions

I would look into using Laravel Actions, designed to do this.

If you have complex business logic or queries that are either too fat for controllers or, especially, you want to re-use in various parts of your app, there are other ways to abstract them. I recently started using Laravel Actions for this, and I love it. You can also use service or utility classes, but I like actions because they help my team keep to the single responsibility principle and write small, refactorable (the real key to good, lasting code) units. The package is also cool because you can use single actions to run the same logic as a controller, a job, a command, etc.

I use plain PHP classes, but there is also a well made package out there, which allows you to queue Actions as well. https://laravelactions.com/

As an extra, one could also work with Spatie's Actions package to make them queueable, or even the full-fledged Laravel Actions package. We kept it simple for now using Plain Old Objects in PHP (POOP).

This is one of the questions Action Domain Responder seeks to answer. The answer for Actions in ADR is the same answer as for a Controller action method in MVC.

First, this is an excellent question. But to answer it, we need to define some terms. Do you mean "action" as in ADR, where the action class is what would have been a controller action method (aka "single-action controller")? Or do you mean "action" as the Laravel folks often use it, a la https://laravelactions.com/ ?

With that in mind, MVU strikes me as being a lot like Action Domain Responder. (I've not heard of MVU before.)

Oh sorry, it means Action Domain Responder, it's a design pattern akin to MVC ( and it's nuances like MVVC ) or DDD. This is the blog of Jones, the person who coined that pattern : http://pmjones.io/adr/

ADR (as opposed to MVC) - direct link - example

Contra /u/dave8271 below, I think it does matter. There are many different ideas about MVC, and as such it's not a very clear vocabulary term, esp. on the server side. The Action Domain Responder pattern exists to help clarify some of those distinctions.

At first I read this as (my paper on) ADR vs MVC. You may wish to consider the ADR pattern over MVC for an API system.

Ah, thanks for saying! As far as one class per route, it's more in line with Action Domain Responder than with what we usually think of as MVC.

This is it: https://github.com/pmjones/adr/blob/master/MVC-MODEL-2.md

cough Action Domain Responder cough