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
Agentforce Commerce
Score 8.1 out of 10
N/A
Salesforce Agentforce Commerce (formerly Commerce Cloud, and Demandware before that) is a cloud-based eCommerce solution for enterprises with merchandising tools, such as sorting, filtering, and image zooming, allowing customers to browse products.
$4
per month
Pricing
Red Hat OpenShift
Salesforce Agentforce Commerce
Editions & Modules
No answers on this topic
No answers on this topic
Offerings
Pricing Offerings
Red Hat OpenShift
Agentforce Commerce
Free Trial
Yes
No
Free/Freemium Version
Yes
No
Premium Consulting/Integration Services
No
No
Entry-level Setup Fee
No setup fee
No setup fee
Additional Details
—
B2B Commerce:
Starter - $4 price/order
Growth - $6 price/order
Plus - $8 price/order
B2C Commerce:
Starter - 1% Gross Merchandise Value
Growth - 2% Gross Merchandise Value
Plus - 3% Gross Merchandise Value
B2B2C Commerce:
1% Gross Merchandise Value
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.
Global Sites; larger commerce organizations but not too large where the % rev-share would affect its feasibility in a feature comparison. Salesforce is rock solid in infrastructure and rarely has outages or issues; it scaled appropriately for holiday peak and was able to accomplish anything we put our minds to as long as we staffed development appropriately. The latter, however, is not to be overlooked. Developers are necessary and expensive.
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.
Traffic - When we have sales, our traffic will increase exponentially and their cloud can handle the huge uptick in traffic we receive without overloading our servers.
Site updates - it continually monitors in the background for any upgrades or updates needed so we don't have to go in and do it ourselves. A real time saver!
Integration - outside plugins and add-ons are easy to install with Salesforce commerce cloud as it allows a seamless integration of extra plug ins onto our site.
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 UX within the Business Manager portion of Demandware, the primary interface for marketers, is generally a confusing, inconsistent mess. Particularly infuriating are the lack of consistency for search and sort behavior within the tool.
A number of useful features, such as the ability to set schedules or tie features to unique customer segments, have seemingly arbitrary limitations imposed.
Demandware's idea of leveraging the community to be a learning resource and a sounding board for new ideas and features is a nice theory, but in practice it doesn't work for businesses with a lot of customization. I'm left with the impression that individual support is not a priority.
OpenShift is really easy of use through its management console. OpenShift gives a very large flexibility through many inbuilt functionalities, all gathered in the same place (it's a very convenient tool to learn DevOps technics hands on) OpenShift is an ideal integrated development / deployment platform for containers
A huge factor influencing our decision to remain on the Demandware platform is that our new parent company is standardizing all its luxury brands in the US on it. We are fortunate. However, even if we had remained an independent company, I believe we would continue on the Demandware platform for all the reasons outlined in this review. I appreciate the stability the platform has provided to our eCommerce site in the last three years as well as the continuous improvements and technological advances being rolled out that will allow us to keep the site fresh, engaging, modern and stable. I've heard many horror stories from colleagues on other platforms who struggle with the expense and complexity involved with making what should be minor and simple changes and updates to their sites.
The virtualization part takes some getting used to it you are coming from a more traditional hypervisor. Customization options are not intuitive to these users. The process should be more clear. Perhaps a guide to Openshift Virtualization for users of RHV, VMware, etc. would ease this transition into the new platform
The overall ease of using the system. Consolidation in location for our team members. Mobile application for on the go research, as many of our team members are constantly traveling to job sites or to meet clients. No more duplicate calls to current customers, since we have 12 different divisions that span the company. Mostly the ability to look at the database when our team members begin cultivating a new lead/prospect with a potential customer to see if anyone within the team has a relationship with that person or the company they work for.
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.
Every time we need to get support all the Red Hat team move forward looking to solve the problem. Sometimes this was not easy and requires the scalation to product team, and we always get a response. Most of the minor issues were solved with the information from access.redhat.com
They are very responsive and a support technician will be assigned quickly. Even if there is further clarification needed for the ticket, or a solution is not immediately available, you feel that someone is there and staying on top of the issue. Most common issues are resolved quickly and satisfactorily.
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.
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.
When I think of Salesforce products, I sometimes think of them interchangeably as one big lump. It's hard not to be incredibly immersed in the ecosystem day in and day out and taking advantage of resources like Trailhead. While Microsoft Dynamics compares in quality and offerings, it doesn't offer the same engagement and resources as Salesforce in its communications, social, and marketing, which makes a difference in terms of relevance and help. Commerce Cloud comes with the support you need to succeed and the tools you need to grow. In a high demand consumer world, we need products like this to keep up and get ahead. The minute we catch up, we're behind. Salesforce helps you stay on pace and create the unique and personalized experiences customers everywhere expect.
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
All of the above. Red Hat OpenShift going into a developer-type setting can be stood up very quickly. There's a very short period to have developers onboard to it and they're able to become productive much faster than a grow your own type solution.
