Large organizations, typically spread across various geographical regions, has multiple lines of business, work through multiple channels, and provide services for multiple products. Such large applications need to handle a large variety of business rules for different regions, products, channels and line of business
Problems with traditional programming approaches to solve such issues
- Ether Create multiple copies of the same code for each variation
- Logically handle such large variations in code using very complex if-else logics.
Both approaches are not suitable in terms of reusability, scalability, performance, and maintenance of code.
Pega Introduced the Situational layer cake architecture to resolving such issues. As per this architecture, development components are organized into layers based on reusability.
Pega situation layer architecture is implemented using Pega Enterprise class structure
Pega situation layer architecture is implemented using Pega Enterprise class structure
Based on reusability Pega can be layered into 4 types of layers
- Pega Platform layer - Pega default rules and data instances
- Enterprise layer
- Division layer
- Framework layer
- Implementation layer
0 Comments