We've got a requirement to upgrade from AEM 6.4 to AEM as a Cloud Service. Though the environment upgrade is fine, the CIF connector and commerce code does not work as is within the upgraded environment. Please suggest if AEM commerce code can be tweaked as per new project structure to work with AEM cloud Service and if 'Repository Modernizer' can be used for same. OR it would be better to re-write all the customizations (mainly frontend code) based on latest archetype.
The venia sample code have two profiles for cloud and classic. Could anyone suggest what's the technical difference between these two profiles and if the same codebase can be built for both cloud & classic then possibly can we also adjust our commerce code from classic to cloud compatible?
Venia Reference Store: https://github.com/adobe/aem-cif-guides-venia
Venia Storefront is a sample reference implementation that supports both AEM as a Cloud Service (cloud profile) and AEM 6.5 (Classic profile)
Now that you are working on upgrading the code base to AEMasCS, we should use cloud profile.
Useful links from Adobe Docs related to this subject: (Ignore, if you have already checked)
Major difference between these profiles is the dependencies. Classic profile uses artifact named "uber-jar" while AEMasCS/cloud profile uses artifact named "aem-sdk-api"
Also with respect to this context, there are some excludes in config specific to profile as evident from ui.config, ui.content and ui.apps modules.