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.

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.

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

I’ve looked into most ecommerce packages for Laravel and they’re all far behind the packages for other frameworks, like Symfony’s Sylius or JS’s Medusa.

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/ ?

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.

What server-side developers have come to think of as MVC might be reasonable, but (as others here have noted) MVC does not really exist on the server side. This is why.

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.

cough Action Domain Responder cough

AutoRoute addresses those problems with a solution more oriented to Action Domain Responder:

without me going off on a massive tangent about it let me just say that the thing you are calling a View isn't really a view it's a template. MVC is a pattern designed for realtime gui applications which has been shoehorned badly in a web context. If you are new to web development it's worth reading up on the Action Domain Responder pattern which is a much better revision of Web-MVC: https://github.com/pmjones/adr

ADR (similar concept to MVC, but more for web apps) - https://github.com/pmjones/adr