Item: Pega Platform
Rating: 7
Author: Verified User

Use Cases and Deployment Scope

Pega is used for Workflow type applications as well as to leverage Pega's Rapid Application Development. Pega is used by many applications where Pega's inbuilt capabilities like Work Management (work basket, Worklist), assignment, SLAs, Decision rules, latest UI features etc are required. Pega also provides integration support as well as option to expose services from the Pega app.

Pros and Cons

Rapid Application Development providing quick UI, business logic development
Stable runtime environment to create applications
Lot s of reusable features available which is required by business apps

Performance is an issue faced with Pega Apps
Could provide a better way to isolate UI vs Business Logic vs Data so required feature can be used alone
Initial startup/warmup is an issue and prevents scaling up

Return on Investment

Ensured successful implementation of projects to go live with isolating technology-related failures
Good for Division level apps with limited userbase

Alternatives Considered

Appian

JBPM

IBM BPM

Activiti

Other Software Used

Mule ESB, Apache Tomcat

Likelihood to Recommend

- Workflow based apps where the work is routed to multiple parties for actions or approvals - But not simple user based apps without multiple assignments

- Structured flow and decision rules etc are involved - Not complicated logic

- Departmental apps with 100 of users - but not for external facing apps with a large number of users

Pega - Good for Internal use with limited userbase

Overall Satisfaction with Pega Platform