How does pega utilises this ECS ?Why exactly is it used?
Why build Enterprise Class Structures?
- Pega is an enterprise software. Therefore, we must design applications with re-usability and scalability in mind.
- As an integral part of every Pega application, the Enterprise Class Structure (ECS) design pattern is the basis for divisional and enterprise-wide reuse.
- Pega offers both pattern inheritance and directed inheritance. This two mechanisms combined provide superior flexibility for reuse. The ECS leverages both mechanisms.
Why using the Best Practice Enterprise Class Structure?
-
Avoids name space collisions and allows Pega apps to co-exist with each other and with Pega and 3rd party frameworks.
-
Allows applications to integrate with legacy systems.
-
Enables you to harness the power of Pega by taking full advantage of specialization & reuse in your design.
-
Helps avoid costly re-factoring.
-
Is the class structure that the Application Accelerator generates.
Hi @TanyaS58,
The Enterprise Class Structure in Pega is an essential design framework that ensures efficient, scalable, and maintainable application development. By organizing classes into a logical hierarchy that reflects the business structure, ECS promotes reusability, enhances maintainability, improves scalability, and facilitates governance. Pega utilizes ECS to create a layered architecture where enterprise-wide, division-specific, and application-specific assets are clearly defined and managed, aligning IT solutions closely with business needs and ensuring long-term efficiency and effectiveness.
Regards,
Prasad.
@TanyaS58 Enterprise Class Structure design is an integral part of every Pega application.
Designing a scalable, extensible enterprise class structures from the beginning of your project will help avoid costly re-factoring. The enterprise class structure enables PRPC applications to co-exist with each other and with customer or Pega built frameworks. The enterprise class structure is also the foundation for enterprise reuse. Asset reuse is integral to the long-term success of BPM within the organization, and ultimately, the reusability requirements drive the selection of your class hierarchy design.
let suppose ICICI is a organization trying to build different domain software what exactly ICICI will do it will be as organization try to create different product across all domains like
Mutual Funds, Loan, Insurances etc.
- Each product will have its own database but also it will share the data across whole organziation from top layer,To support directed and pattern inheritance pega supports ECS
- ECS is not a rule its a concept to understand pega way to design the application , understand the pega way to extend the application across division wise, country wise . Like amazon application has same UI across all the country state etc.
- ECS helps to create a structure in that sharing of rules become so easy to manage the rules.