adr VS slim4-skeleton

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

You can have the container call in a config folder with a file called dependencies or how ever you want. A few existing examples of this is here - Slim calls this app/dependencies in this skeleton project and Odan's Skeleton has this as config/container in their project.

Yes, as an example, the First Application's business logic (not that it's much) doesn't tie itself to the framework, as one example. Odan's Slim Skeleton, ADR Example (yes, I know you are the author), and the Aura Payload example class can be seen as other examples.

Even just the tests in your first link are very useful to see, such as: https://github.com/odan/slim4-skeleton/blob/master/tests/TestCase/Action/Customer/CustomerCreatorActionTest.php

Another option, to me and speaking to the OP as an alternative, it is simpler to add some Data Mappers/Repositories to abstract away the Database code. Good examples is the sample ADR application, Payload library example, Slim 3 First Application, or this Slim 4 Skeleton application

You could also use a Slim Skeleton like Odan's which incorporates much more features to help - docs.

Try Slim again. The setup may be too much, but the concept is the same. Look at the first application or any of the skeleton apps to help (https://github.com/odan/slim4-skeleton for one).