IBM Cloud Pak for Applications vs. ServiceNow App Engine

Well suited for customers who are looking for cloud-adoption, and finally to meet the challenges of business innovation for the competitive advantage through DevOps.

Incentivized

I suggest that people in ServiceNow start by building apps in App Engine through learning plans on the ServiceNow Developer site. It is a very guided process, and it is fun to do. Newcomers in ServiceNow can learn a lot about configuring tables, fields, behavior of fields, roles, Flows, UX, and many more. App Engine tends to make development work simpler and faster to ship. However, it can be a difficult concept for people new to ServiceNow to understand scoped applications. So there should be a brief on the App Engine homepage that mentions what can be built and includes a link to learn more about scoped apps.

Incentivized

• Provides a fantastic range of Application runtimes allowing the most suitable runtime to be selected for the app being implemented.
• After using Transformation Advisor for quite a while, it is an indispensable tool to help modernize, specifically from WebSphere and Tomcat, towards the lightweight, fast and efficient Liberty runtime.
• The simplicity of the licensing by wrapping many products into a single offering with a different VPC weighting.
• Allows us to modernize our runtime from WebSphere Application Server (or ND) to WebSphere Liberty core without sacrificing our WAS licenses.

Incentivized

• App Engine can be used by non-developers to create Applications on the go, without coding.
• App Engine has all the important aspects of the application available for adding or editing within a single record. Hence, it is easier to modify.
• App Engine has a delegated development option which can be granted to specific developers or groups to manage a specific area for Scoped App Development without giving admin rights.

Incentivized

• User Experience and Learning Curve
• Integration with Third-party Tools
• Pricing and Licensing Model

Incentivized

• The scoped app prefix should be shorter to allow appropriate application naming if it exceeds the character limit. Either the scoped app name limit shall be increased, or the limit on scoped app prefixes shall be increased to allow better naming for scoped apps.
• It's challenging to make citizen development work at scale. Businesses want experienced pro code developers rather than citizen developers to work on this feature.

Incentivized

There are limited use cases where we are just using the service now app engine as of now

Incentivized

Overall, very much usable for anything that happens in organisation. Able to track and discover each asset in the underlying infrastructure of the organisation and manage them. It is easy to understand the impact if any asset fails and hence risk mitigation becomes easier. It is a simple tool but with everything an organisation requires to go live with maximum customer impact and satisfaction

Incentivized

Almost 100% available on time

Incentivized

They tried their best to resolve our queries every time we contacted them about any technical support

Incentivized

App engine can be used just to process the minimal amount of the data which is being received from the user. We are service now catalogue items or any other data technology.

Incentivized

Our customer mission-critical core banking applications like Temenos T24 run on best of the breed IBM WebSphere Application Server which is java based-application server. IBM has kept up the promise of providing support, fixpack, and any update. As far as I know, at least by 2030, IBM is committed to continue with WHE which gives customers confidence in their current investments.

Incentivized

There were no options from the other products because ServiceNow App Engine is a large product with many different modules, growing each year, which allows you to recreate your business processes in a very short time, making the migration to ServiceNow very easy.

Incentivized

It is scalable but not reliable

Incentivized

• We have been able to migrate apps away from the expensive WAS-ND to the more cost-effective WAS-base without throwing away our WAS-ND licenses. With a 1:4 ratio of WAS-ND to WAS-base we've been able to we've been able to save in excess of 75% on licensing charges for these apps.
• By having a license model based on VPC ratios (1:4:8 - WAS-ND:WAS-base:Liberty core) we've been able to move away from using license pooling resulting in over-allocating (i.e. wasting) CPU cores for each license pool, to using consolidated license pools hosting a combination of WAS-ND, WAS-base and Liberty-core. This has allowed us to reduce our licensing costs accordingly.

Incentivized

• We have managed to close the un applied cash item from 56% to 89% in a given five working days period by using ServiceNow App Engine
• By automating and entire money laundering process, we have managed to provide the background check data as quickly as within a day, which was actually taking weeks Same reports when we were doing the things manually.

Incentivized