Question

4
Replies
35
Views
William Baeyens (baeyw)
PEGA
Sr. System Architect - Pega Consulting
Pegasystems Inc.
FR
baeyw Member since 2019 8 posts
PEGA
Posted: April 25, 2021
Last activity: May 3, 2021
Posted: 25 Apr 2021 6:15 EDT
Last activity: 3 May 2021 11:43 EDT

LSA Course : "Framework" VS "Component Application"

Hello, 

It seems to be overall recognized that using a "Framework" is not a viable design choice unless under very specific circumstances. 

For example, the course says: "When using the New Application Wizard do not use the "Framework" option purely for the sake of future-proofing. Maintaining a framework comes at a cost that cannot be justified without clear evidence for its need. "

I'm having a lot of trouble understanding why the same reasoning does not seem to be applied in regards to component applications. 

In my view, a component application does not differ much from a framework. It's just the logical evolution of a framework since Pega allow multiple built-on application. 

It's still a "reuse layer" that can be specialized. 

So my question would be in what kind of situation should a component application be recommended over simply having 1 ruleset per case type? Should it follow the same reasoning as for the framework? Aka a clear requirement for reuse?  Or just the fact that some functionalities "go together" justify the choice of making a component? 

 

Kind regards. 

 

 

Pega Platform 8.5.3 Pega Academy