For example, an e-commerce site, where there are a "region" for the sellers, with feature align to managing products or selling analytic. And a front-facing "region" for regular clients to browse the products, have a cart, bookmark or follow products or brands https://routerlogin.uno/ .
When there are 2 (or more) distinct regions for different functionality and client. How would you structure your Laravel project? Would you follow DDD? Microservices? Or something else?
To be clear it is not strictly e-commerce, but any systems that had multiple regions like that. A travel agency where there are region for hotel owner to register and manage their hotel versus a region for everyone to search and book hotel. A streaming app where everyone can browser their favorite streamer but the streamers have their own managing place as well as analytic... Also count.
By region, I take it you mean sections of a website, rather than geographical regions?
For my ecommerce platform I just do a regular monolith multi-page app. I use different layout components for sellers and customers. And obviously sellers have a whole extra admin area. Works well for my use case.
Please or to participate in this conversation.