@SureshP16655111 If the entire application size is getting too big, you could separate your pipeline per application.  For example, you could have a separate pipeline for your enterprise layer application and another pipeline for your implementation layer application.  I've seen some projects having a separate pipeline per component application.  In my project, we have different dedicated pipelines for BIX, SSO, Questionnaire, etc.

On your other question regarding a data instance update during deployment, you may want to review this article - https://docs-previous.pega.com/devops/86/managing-aged-updates-1?.  In my current project, we use "Override" by default, which can be a more aggressive approach but reduce manual updates; any update in DEV will automatically override in higher envs during deployment.  But sometimes clients may want to choose "Skip" and update data instances manually in different environments.

FYI - we use DM 5.5.6 and Platform 8.8.4.