Good Day,
Can you please share some thoughts on what would be the best way to achieve the following:
My current train of thought is to have one “Container Application” that will manage the generic sections that apply through any of part of the application, such as user authentication and user profile sections.
This will also maintain the Menu section.
Each item on the menu is a completely separate ionic application and are all built and deployed separately.
When you click on the menu item however, that application is opened within the container application.
Like this:
The main reason why I was considering using this approach is to have a fully decoupled approach - in that one application has no effect on another but all share the same common items provided by the container application.
In theory this sounded great, but I am wondering if this design is not going to be more trouble than it is worth and if it would be better to create just one application with different components for each application.
All applications are integrated with lambda and dynamodb, so the decoupling on those areas still remain unchanged.
Your feedback and thoughts are much appreciated.
Thank you in advance!
1 post - 1 participant