Sylius VS adr

I think it would be difficult (or much harder) to build something like Sylius on top of Laravel. Especially if you want good code-coverage by tests.

For the development of high-scaling applications and responsive websites, open source headless commerce architecture has become the go-to option in recent years because of its flexibility, scalability, and agility. However, choosing the best open source headless ecommerce platform can be challenging. To help you navigate this complex landscape, this article compares two popular open source solutions: Medusa and Sylius.

Checkout Sylius. Try to run it and modify it in some way. Pretty big codebase and project. If you can modify it without directly rewriting the Syius code (like overloading Symfony services and so on...) you can be confident in your skills.

Can you tell me what exactly is wrong in language with code like this? Do note that this is still old <7.4 version, and version 8.0 and 8.1 gave us many goodies like constructor promotion, match, enums, throw expressions...

Just go with Shopify/Vercel. I've been hearing nice things about https://sylius.com/ too.

Sylius: https://sylius.com/

I would say Sylius is your best bet: https://github.com/Sylius/Sylius but I am sure there are many more.

Take a look at this: https://sylius.com/ it's opensource, based on Symfony and might be better than everything you mentioned.

Not sure what your needs are but yes I would use a framework and since you mentioned e-commerce I would take a look at this: https://github.com/Sylius/Sylius

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