What is the ideal way to work with modules in this new architecture? about docs HOT 6 CLOSED

Depends on what do you mean:

1. If you mean "how to organize my code" then the answer is by namespace. There's no need in specific modules anymore. Entry points could be anywhere.
2. If you mean reusable modules then these are packages now. They are again, just a set of classes. The only difference is about configs. They could provide configs like https://github.com/yiisoft/cache-file/tree/master/config via Composer config plugin https://github.com/yiisoft/cache-file/blob/master/composer.json#L48

from docs.

Yii 3 allows all that without having to create modules. See how classes are grouped together by use-case: https://github.com/yiisoft/yii-demo/tree/master/src/User. Later we may come up with extra functionality to make it even more convenient.

from docs.

Thanks for your quick response @samdark. I was referring to this fabulous feature: https://www.yiiframework.com/doc/guide/2.0/en/structure-modules as it was very efficient when working with monorepositories.

from docs.

@j1myx which features exactly?

from docs.

I mean the complete decoupling that a module had from the entire web application. Since having the views, controllers, etc. separate from the rest of the application, it made the project structure more neat. This order had many advantages considering that yii2 used it a lot in monorepos projects, for example, the joint work of n programmers.

Apparently this architecture was born to cover microservices, leaving aside how well the previous architecture worked to work with monorepos.

from docs.

Thanks for the info @samdark . I really appreciate the enormous effort
doing to improve this great framework.

from docs.