CloudFoundry vs. SAP Integration Suite

It's well suited if:

• The organization has large number of applications that needs to be deployed frequently.
• The organization is tied to the DevOps mindset.
• The organization has programs in different languages.
• The applications does not need EJB's support that servers like web logic provide.

It's less suited if:

• The applications needs security configuration within the same CloudFoundry instance.
• The organization, for whatever reason does not want developers to manage the instances.

Incentivized

E-commerce Integration:Scenario: An e-commerce business utilizes SAP Integration Suite to integrate its online storefront with back-end systems. This includes connecting order processing, inventory management, and customer relationship systems to ensure a smooth and efficient order fulfillment process.Real-time Analytics and Reporting:Scenario: A retail organization utilizes SAP Integration Suite to enable real-time analytics by integrating data from multiple sources. This includes POS systems, online sales platforms, and customer feedback applications, providing timely insights for informed decision-making.

Incentivized

• Support for Orgs and Spaces that allow for managing users and deployables within a large organization.
• Easy deployment, deploying code is as simple as executing single line from CLI, thanks to build-packs.
• Solid and rich CLI, that allows for various operations on the instance.
• Isolated Virtual Machines called Droplets, that provide clean run time environment for the code. This used to be a problem with Weblogic and other application servers, where multiple applications are run on the same cluster and they share resources.
• SSH capability for the droplet (isolated VM's are called droplets), that allows for real time viewing of the App code while the application is running.
• Support for multiple languages, thanks to build-packs.
• Support for horizontal scaling, scaling an instance horizontally is a breeze.
• Support for configuring environment variable using the service bindings.
• Supports memory and disk space limit allocation for individual applications.
• Supports API's as well as workers (processes without endpoints)
• Supports blue-green deployment with minimal down time

Incentivized

• The drag-and-drop interface, as well as SAP regular improvements to its pre-packaged content, are also excellent features.
• The security features (such as the cloud connection for sending data to the local system, as well as encryption and scrambling) are really beneficial.
• Unlike other tools I've tested, the SAP connectivity package offers access to third-party cloud apps.
• Prototyping may be completed more quickly, and the team can determine whether or not to proceed with the integration depending on the feedback process.

Incentivized

• Does not support stateful containers and that would be a nice to have.
• Supports showing logs, but does not persist the logs anywhere. This makes relying on Cloud Foundry's logs very unreliable. The logs have to be persisted using other third party tools like Elk and Kibana.

Incentivized

• There are some loopholes there by which some problems appears, may be different usage in different modules, as i am working on PP module but we lack sometime with linkage of MM module.
• There are some loopholes there by which some problems appears, may be different usage in different modules, as i am working on PP module but we lack sometime with linkage of MM module.

Incentivized

SAP Integration Suite is very helpful to us in many ways to manage purchase procedures, stocks, and data of vendors and suppliers. Also, it helps to manage data for service providers. SAP Integration Suite has the tool to conduct training and evaluation. Unique features like the cloud can provide access from any place and by any device is very helpful.

Incentivized

It's very easy to use and configure.

Incentivized

Support is hard to reach and takes a long time to get a response.

Incentivized

Work with an SAP implementation partner, if possible.

Incentivized

While Docker shines in providing support for volumes and stateful instances, Cloud foundry shines in providing support for deploying stateless services. Heroku shines in integrating with Git and using commits to git as hooks to trigger deployments right from the command line. But it does not provide on-premise solution that Cloud foundry provides.

Incentivized

I selected it because its now one of the best thing to do and to work. As we are currently working from home it makes the work easy and comfortable and yet the main usage will be in office the environment created will be simple. The UI logic is based on some calculations which will rely on some natural intuations of mind and when it comes to mind it is easy.

Incentivized

• Positive impact, since it simplifies the deployment time by a huge margin. Without cloud foundry, deploying a code needs coordination with infrastructure teams, while with cloud foundry, its a simple one line command. This reduces the deployment time from at least few hours to few minutes. Faster deployments promote faster dev cycle iterations.
• Code maintenance such as upgrading a Node or Java version is as simple as updating the build-pack. Without cloud foundry, using web logic, the specific version only supports a specific version of Java. So updating the version involves upgrading the version of web logic that needs to involve few teams. So without cloud foundry, it takes at least few days, with cloud foundry, its a matter of few mins.
• Overall, happier Developers and thats harder to quantify.

Incentivized

• In the long run will enable us to undeploy our on premise solution
• As long as integration suite doesn't support all capabilities PO has complete migration is hard
• Will probably be cheaper than our on premise solution when we are completely migrated

Incentivized