We used to create a reusable standalone components for integrations which can be used in multiple applications. But recently I read some where that pega is moving away from component approach preferring application to component. I could not find the right article to support this argument. Is this a right understanding if so what are the reasons for this move . Does any one have supporting article on it ?
@SaleeshaPega now recommends using applications instead of components for reusable building blocks because applications offer better control over versioning, access, and lifecycle management. Built-on applications allow sharing reusable rules across multiple applications more effectively than components, which had limitations in rule resolution and governance. Applications simplify deployment and CI/CD processes, making it easier to manage dependencies and package rules with product rules and pipelines. They also align better with Pega’s Constellation UI architecture, which emphasizes modular design through built-on layers rather than fragmented components. Built-on applications support a clearer inheritance model, improving reusability and maintainability. For reusable functionalities like integrations and common services, creating a separate application and using it as a built-on layer is now the recommended best practice
@Sairohith Thanks for your reply. I tried in docs.pega.com . But unfortunately I could not find any article to support the argument. If you read it some where and if you have the link with you please share .
The changes are expected based on industry experiences. Pega’s most experienced lead system architects and business architects, working with Pega’s product engineering team, have developed a modular approach to reuse that focuses on smaller units of reusable modules.