Microsoft's Azure API Management supports creation of API.
$0.04
per 10,000 calls
Red Hat OpenShift
Score 9.2 out of 10
N/A
OpenShift is Red Hat's Cloud Computing Platform as a Service (PaaS) offering. OpenShift is an application platform in the cloud where application developers and teams can build, test, deploy, and run their applications.
$0.08
per hour
SAP Business Technology Platform
Score 8.5 out of 10
N/A
SAP Business Technology Platform (SAP BTP) is the company's Platform-as-a-Service (PaaS) offering, that brings together intelligent enterprise applications with database and data management, analytics, integration and extension capabilities into one platform for both cloud and hybrid environments, including hundreds of pre-built integrations for SAP and third-party applications.
N/A
Pricing
Azure API Management
Red Hat OpenShift
SAP Business Technology Platform
Editions & Modules
Consumption
0.042 per 10,000 calls
Lightweight and serverless version of API Management service, billed per execution
Developer
$48.04
per month Non-production use cases and evaluations
Basic
$147.17
per month Entry-level production use cases
Standard
$686.72
per month Medium-volume production use cases
Premium
$2,795.17
per month High-volume or enterprise production use cases
Isolated
TBA
per month Enterprise production use cases requiring high degree of isolation
We found SAP Business Technology Platform to be the most effective platform for extending and integrating our SAP ecosystem. While other cloud platforms like Azure excel in open innovation and broad infrastructure capabilities, SAP Business Technology Platform delivers the best …
SAP BTP brings a "business" context to everything. As a result, it is well suited for a business audience. But they often lack technological know-how and so adoption becomes difficult.
I felt API gateway is superior when it comes to DevOps integration and the number of connectors and customization, while SAP ChatBot really is a cool product and can easily triumph over AWS Chatbot or azure ChatBot. Even Sap Analytics cloud can be a real competitor for power …
1) Securing your back-end APIs - If you have a legacy back-end web service that has a basic authentication scheme, you can add some additional security by placing APIM in front, and requiring subscription keys. Leverage your existing firewall to ensure only your APIM instance can communicate with your back-end API, and you've basically added a layer of protection.
2) Lift and shift - there are always going to be clients that don't want to update their clients to use a newer API; in some cases you can make a newer API look like an older one by implementing some complex policies in APIM. You can also do the opposite, making older APIs look new, such as making an XML back-end accept both JSON and XML.
3) Centralizing your APIs - if you've acquired another company and want to make their API set look as if it's a part of the larger whole, APIM is an easy way to provide a consistent front-end interface for developers.
Red Hat OpenShift, despite its complexity and overhead, remains the most complete and enterprise-ready Kubernetes platform available. It excels in research projects like ours, where we need robust CI/CD, GPU scheduling, and tight integration with tools like Jupyter, OpenDataHub, and Quiskit. Its security, scalability, and operator ecosystem make it ideal for experimental and production-grade AI workloads. However, for simpler general hosting tasks—such as serving static websites or lightweight backend services—we find traditional VMs, Docker, or LXD more practical and resource-efficient. Red Hat OpenShift shines in complex, container-native workflows, but can be overkill for basic infrastructure needs.
If you want to use a well-designed SAP technology to shift into the cloud, you will be more than satisfied with the BTP services overall. There are some improvements for beginners to help them get a better overview of what to do and how to start with their account. My recommendation is to take a foundation training course from the SAP learning hub to prepare for the first steps.
We had a few microservices that dealt with notifications and alerts. We used OpenShift to deploy these microservices, which handle and deliver notifications using publish-subscribe models.
We had to expose an API to consumers via MTLS, which was implemented using Server secret integration in OpenShift. We were then able to deploy the APIs on OpenShift with API security.
We integrated Splunk with OpenShift to view the logs of our applications and gain real-time insights into usage, as well as provide high availability.
All the documentation around it is geared towards the enterprise use case, unlike some other hyperscalers' platforms.
The SAP Business Technology Platform is very good because it's got the SAP customer and their business processes in mind. Probably my favorite thing about it is how easy it is to get up and running with a new use case and how well it natively connects to an SAP solution.
Lack of robustness is a bit of an issue. Several other providers offer more options and capabilities, but then, they are lacking in interface ease.
As with anything Azure, pricing is really hard to stay on top of. I always find that you really don’t know what you’re paying for until you get the bill. Having an excellent Azure Administrator can help resolve that.
Integrating with app services outside of Azure can be a challenge, or at least much more challenging than just using Azure App Services.
I wouldn't necessarily say there is look everyday technology transform. I can see a trend wherein Red Hat OpenShift is adopting all the new technology trends and helping their customers align with their priorities and the emerging technology trends. I wouldn't call out various scope for development every day. There is scope for development. It is all how the organizations adopt it and how they deliver it to their customers. I don't want to call out there is scope for development. It's happening. It is a never ending process.
At the moment, I don't have anything to call out. We are experiencing Red Hat OpenShift and we can see every day they're coming up with new features as and when they come up with new features, we want to experience it more and more. We are looking for opportunities wherein this can be leveraged to help our users and partners.
The Automation Integration service has some outdated workflows
New services should be available as entitlements as soon as they are released for a particular region without having to buy them from SAP for zero dollars
Any subaccount should be able to change the IAS tenant. Currently, if you set it up for a particular IAS, you cannot change to another tenant and are required to recreate the services in a new subaccount.
This is the current strategy for the company, most of the products in the organisation are aligning to Openshift and various use cases it support. Also lot of applications are being developed for AI use case, openshift.AI provides opportunity to host and leverage the AI capabilities for these applications
Seamless integration with external system and dashboard to monitor the data flow and analysis are very essential for the business. The way the product is designed and modelled lead to minimum business disruptions. Adopting to the new and modern technology was easy. Keeping the central system as clean and adopting project bases development are advantages.
As I said before, the obserability is one of the weakest point of OpenShift and that has a lot to do with usability. The Kibana console is not fully integrated with OpenShift console and you have to switch from tab to tab to use it. Same with Prometheus, Jaeger and Grafan, it's a "simple" integration but if you want to do complex queries or dashboards you have to go to the specific console
Okay, so the content that we have built on the platform is limited to specific testing on the iFlows within integration suite. The visualization layer is nice to use and helps with the design elements, however with developers that are more used to markup languages, it doesn't have the same CLI type feel when you want it. Perhaps the majority of users are that deep, but other platforms have a better CLI type developer experience.
Redhat openshift is generally reliable and available platform, it ensures high availability for most the situations. in fact the product where we put openshift in a box, we ensure that the availability is also happening at node and network level and also at storage level, so some of the factors that are outside of Openshift realm are also working in HA manner.
Overall, this platform is beneficial. The only downsides we have encountered have been with pods that occasionally hang. This results in resources being dedicated to dead or zombie pods. Over time, these wasted resources occasionally cause us issues, and we have had difficulty monitoring these pods. However, this issue does not overshadow the benefits we get from Openshift.
Their customer support team is good and quick to respond. On a couple of occassions, they have helped us in solving some issues which we were finding a tad difficult to comprehend. On a rare occasion, the response was a bit slow but maybe it was because of the festival season. Overall a good experience on this front.
The biggest problem we ran into was communication between SAP Business Technology Platform and onsite resources. Unfortunately our SAP Business Technology Platform and Cloud systems are under different customer numbers. I constantly had to open tickets under each customer number because I was unsure of where the issue lied. And having to create a dummy ticket for our ECC systems to open the ECC connections for another ticket under the Cloud customer is a pain.
I was not involved in the in person training, so i can not answer this question, but the team in my org worked directly with Openshift and able to get the in person training done easily, i did not hear problem or complain in this space, so i hope things happen seamlessly without any issue.
We went thru the training material on RH webesite, i think its very descriptive and the handson lab sesssions are very useful. It would be good to create more short duration videos covering one single aspect of openshift, this wll keep the interest and also it breaks down the complexity to reasonable chunks.
Training material in Developers Community or from Learning hub are really good... also most of the time we route through Discovery center... so materials provided by SAP is really good.
Having a full cloud native environment for devlopment of microservices and digitals solutions while having standardized access to our core data on SAP via cloud connector is one of the main benefits of using BTP over others hypervisors. BTP is the standard hyperscaler as soon as something relies on data from SAP systems in our company now
The Tanzu Platform seemed overly complicated, and the frequent changes to the portfolio as well as the messaging made us uneasy. We also decided it would not be wise to tie our application platform to a specific infrastructure provider, as Tanzu cannot be deployed on anything other than vSphere. SUSE Rancher seemed good overall, but ultimately felt closer to a DIY approach versus the comprehensive package that Red Hat OpenShift provides.
SAP Concur allows our staff to book, reimburse and remain spend audit compliant. Our Concur system takes feed from Workday and interacts with Credit card vendor. It also makes posting to Accounting and does clearing. SAP Business Technology Platform helped in establishing connection with all these different tools in real time. It helps in getting paid to the card service provider through our Bank through interface, which is built on SAP Business Technology Platform.
It's easy to understand what are being billed and what's included in each type of subscription. Same with the support (Std or Premium) you know exactly what to expect when you need to use it. The "core" unit approach on the subscription made really simple to scale and carry the workloads from one site to another.
This is a great platform to deployment container applications designed for multiple use cases. Its reasonably scalable platform, that can host multiple instances of applications, which can seamlessly handle the node and pod failure, if they are configured properly. There should be some scalability best practices guide would be very useful
That is a complicated question and one that's not easy for me to answer. There's a lot of factors that go into all of the stuff that we just don't have an easy way of measuring. And we realize that while we're implementing Red Hat OpenShift, we've tried to start measuring some of that stuff, but we don't have a baseline to go on. So it's hard to say. What I can tell you is general experience with the platform has been extremely positive from the development aspect. Teams have been very, very happy with the speed at which they're able to do stuff. They've been happy with that. The way it works in one environment is exactly the way it works in the next environment because we don't have configuration drift, that type of thing, and has had very positive impacts. But we didn't have a baseline to start with. So I can't talk about getting there faster or anything like that.
Infusing Generative AI capabilities easily into our solutions with existing talent with minimal learning curve, has been very impactful. We have been able resolve several challenges for our clients with AI capabilities, that we could not, previously.
Integration Suite is quite extensive in capabilities for bringing together the IT landscape into a single ecosystem.
