Problem Description: We have a big monolith app containing UI components A,B,C,D. You can think of a component as a page for now. Component A & B share a sub-component called SHARED. Now both A & B are planing to move out of the big monolith app. The challenge here is to have same look and feel for sub-component SHARED in both A & B at all times.My Solution: Publish the sub-component as module. Both A & B import it and use it. The problem here is whenever a new version of sub-component gets published, both A & B would need a release. Releasing both A & B at the same time won't be straight forward. This needs co-ordination between the teams that maintain A & B respectively. There may be a possibility when A got released but B had to rollback because of some other breaking change. This scenario violates our requirement of consistent look and feel for the sub-component across A & B at all times. There would be other similar scenarios too. How should we handle this?Is there a better way to handle this situation?
Design Problem: Breaking down a monolith web application
design;web applications