Replies: 3 comments
-
The FE (Vue app) could be served by some other structure (Caddy, Nginx) and the node API continue on it's own. |
Beta Was this translation helpful? Give feedback.
-
My general developer experience is I find the nested structure confusing to understand from an architectural perspective. Many of the build configs have the Vue frontend build hidden within the API build (which caused a couple of issues for me not being initially aware of this). I also ran into issues with using a different test framework for the Vue frontend which required some additional configuration. My thoughts (and this is strictly my own opinion) is that I favour having clear boundaries and explicit separation between the API and the Vue frontend (unless there is some clear reason I've overlooked here). I think this also makes sense from a scalability perspective to have both separate. I do however see a reason to keep the nested structure for those that don't want to now deal with deploying multiple services. |
Beta Was this translation helpful? Give feedback.
-
A pattern we've used in several other projects it to serve out the FE on a pod that also acts as a proxy server to the backend API. This way you have a single URL for the application and from the outside it looks like a single app. Example; https://github.com/bcgov/orgbook-bc-client This allows you to resource and scale the services separately as needed. |
Beta Was this translation helpful? Give feedback.
-
TBD
The Tenant UI was developed to :
Some of this could be rethought if necessary, as the Vue app is pretty standalone at this point.
Beta Was this translation helpful? Give feedback.
All reactions