adr VS router

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

I've found bramus/router to be pretty convenient for migrating projects. It has middleware support, so it's easier to migrate your authorization/authentication stuff.

As an example with bramus/router:

I just use a router like Bramus together with a PDO wrapper and my views are just old-school PHP templates (no Twig/Blade/Smarty). For logging check out monolog.