Hi, Is it normal to split weweb development into multiple projects that service the same custom domain?
For example a project for course delivery and another project for the admins to perform functions about the course delivery?
Or can it be done on 1 project and it just grows bigger with all its global variables (which can be harder to wade through).
I welcome any feedback as to which way as to best practices?
For our part, we have decided to split the application into 3 different web projects.
They all use the same backend, but we quickly switched to this solution for reasons of maintainability and release impact. In fact, our 3 applications are quite different from each other, which justifies this decision.
To better manage security constraints on the backend, each application has its own endpoints.
If we change an endpoint on the backend, we may only affect a single app.
Backend performance is better because we don’t have to manage different scenarios on each endpoint depending on the needs of each application.
That also has merit with your reasons for splitting the application into 3 different web projects.
My question with this pathway - could it still service different parts of the same domain website?
I assume multiple projects could work on the same domain in its own way?
Hi, Also, when it comes to the various plans, which ones allow for three or four separate live projects to be active at the same time?
When I look at the project plans (Starter / Scale, etc.), I can’t seem to find clarity as I would look to move next to the Starter plan and discover a cap on simultaneous live projects?
Thanking you,