AEM Cloud Multi Brand Project

[Jineet_Vora]

We have single AEM Cloud Program and we have a requirement to have 2 projects (multi-brand) with site-a and site-b. Both the sites would have some common components, services and few distinct as well.

Since AEM Cloud deployment is a docker image based, what is the recommended approach where different teams can work with different release cycles?

Adobe suggests Git Submodule https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-... but is there any disadvantage of using this approach? Any suggestion?

Thank you!

[krati_garg · Accepted solution]

@Jineet_Vora You can have multiple projects as GIT sub modules. Different teams can work on their respective repositories, however, there should be a Syncing mechanism which will pull all the Content from multiple branches and add it to Cloud Manager GIT repository. 
Help document to build the syncing mechanism:
https://experienceleague.adobe.com/docs/experience-manager-cloud-service/content/implementing/using-...

I believe if you have different release cycle for different projects, you might want to set up a governance model to ensure basic Sanity is being performed for all the projects, which are getting live with a project release

[Shubham_borole]

Hi,

 For common services and components, a separate repo similar to Adobe's core component library can be created.

Both project A and B can include core dependencies from custom Core project for utils, services etc. And for components we can use super resourcetype to extend components.