eBA vs. Pega Platform vs. Red Hat JBoss Enterprise Application Platform

Pega Platform has introduced the low code feature, using app studio seasonal and professional developer can develop application easily and quickly. The initial application can be build by Business analyst and product owner who has less knowledge of Pega Platform, further application can be enhanced/extended by professional developer. We can develop end to end application and promote to higher environment. Easily we can perform parallel development using branch.

Incentivized

JBoss EAP is subscription based/open source platform. It's very reliable and great for deploying high transaction Java based enterprise applications. It integrates well with third party components like mod_cluster and supports popular Java EE web-based frameworks such as Spring, Angular JS, jQuery Mobile, and Google Web Toolkit.

Incentivized

• Quick development time. Much of the Pega "rules" are easy to configure and implement.
• Visually friendly and modern. Much of the UI/UX elements in the system are continuously supported and updated, giving a nice feel to the apps.
• Many of the configurations and rules Pega gives to the developers can also be delegated to business users. The organization and structure of the client's business can easily be adapted in the Pega platform.

Incentivized

• MOD_CLUSTER integration. JBoss EAP integrates pretty well with mod_cluster. This is an intelligent load balancer especially useful in highly clustered environments.
• Supports enterprise-grade features such as high availability clustering, distributed caching, messaging etc.
• Supports deployment in on-premise, virtual and hybrid cloud environments.

Incentivized

• Need more learning materials. For Beginners who have previous programming experience with another language takes more time to learn.
• If the developer is met with an issue in pega platform , they have to rely on Pega supporting team to fix it.
• Customization is available but is not encouraged. Pega does not support faults that occur in customized solutions.

Incentivized

• Difficult to replicate configuration outside of a container environment
• Still requires quite a bit of knowledge of the CLI
• Integration with deployment tools requires CLI knowledge

Incentivized

Pegasystems has continued to demonstrate a strong partnership with our organization and investment in their product that aligns with our overall vision and need. Pegasystems has engaged us at every level, with the assistance of minor defects to the overall roadmap planning and alignment of our goals

We are planning to migrate away from Jboss to Tomcat as Jboss has shown not interest in supporting OSGi which is heavily used at our shop

Incentivized

Pega Platform is enhancing its product and launching new features day by day which help to achieve customers needs. If I talk about the earlier version of Pega Platform (i.e. pega v5 and 6.3) there were many numbers of limitations in Pega Platform and if we need to do some customization then needed to write custom java and jave scripts to achieve the functionally. Now I can say Pega Platform is running with market trends and demand. Pega Platform is giving all the options which support the current technologies like decisioning capabilities, real time processing, mashup, process fabrics etc..

Incentivized

JBoss overall is easy to use. The installation and deployment of applications are quick. Documentations and support are also readily available.

Incentivized

JBoss EAP is lightweight and doesn't really consumes much physical resources. It's high performing and suites well for high transaction Java enterprise applications. The out of box performance settings are not really great and you will have to configure the settings to suite your environment to leverage it's full benefits.

Incentivized

It’s very slow sometimes, but that may be our servers. Also the Knowledge Library needs some work - again, not sure if it’s our setup or what- but I’m unable to search the body of an article for content, so I have to be very intentional with tagging, but it’s not ideal.

Incentivized

Fast response.

Incentivized

The online training is an excellent one, but still it is missing hands on development.

Implementation is totally depend up on the requirement

Incentivized

We did evaluate multiple products offerings with Pega Platform capabilities and observed that Pega PRPC rules engine and case management capabilities are better over so many BPM Tools. We also conducted a detailed study with developers to identify the best products out of Suite of BPM products. It's observed that Rules engines integration is very streamlined with forms in Pega whereas other tools multiple have powerful data model capabilities but lacks the ease of creating business rules.

Incentivized

We selected JBoss because of compatibility with EJB's. We currently are trying to reduce our footprint and will highly consider using Tomcat.

Incentivized

• For one of the applications we worked on, we were able to reduce the processing time on a case from 2 days to 20 minutes by utilizing Pega
• We were able to resolve the issue of the routing of cases to users based on a specific algorithm by use of Pega
• Pega case management feature was extensively used in one of the application to establish a parent-child relationship which was very helpful for all the business users

Incentivized

• Jboss EAP is easy to deploy and configure. This lead to lower cost and faster delivery.
• Even though we have large number of machines running JBoss, we have only two Jboss Administrators. It doesn't requires too much administration and maintenance on daily basis and reduces number of administrators required for large implementations.

Incentivized