no-framework-tutorial VS adr

I myself learned by following the great "no-framework-tutorial": https://github.com/PatrickLouys/no-framework-tutorial Disclaimer: The last one is about 7 years old, so some things have changed, but all in all the information there is still valid.

No framework tutorial

Here's an all-in-one github repo that I found to be a nice build for the fundamentals: PatrickLouys/no-framework-tutorial

Use libraries or a micro framework if you are hesitant on using a full framework. Nothing wrong with Slim and some other libraries. Or bundle some libraries together to make your own slim (pun intended) framework - like this or this.

https://github.com/PatrickLouys/no-framework-tutorial also got turned into a book.

This tutorial (and subsequently the book) helped me a lot when learning OOPHP.

Do you already know how backends work? Maybe this can be a good read. Otherwise just look up the basic syntax and some quirks and you will be fine.

Search for "PHP without a framework" to find articles such as https://github.com/PatrickLouys/no-framework-tutorial that will show you how to "fill in the blanks" with libraries or simple code, or use a "microframework" such as Slim.

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