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
Sitecore Digital Experience Platform
Score 8.7 out of 10
N/A
The Sitecore Experience Platform (Sitecore XP) is a digital experience platform used to build websites and create customer experiences online. The solution boasts fast content authoring, built-in personalization features, testing and other optimizations, as well as analytics and marketing features.
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.
Sitecore offers Content Hub with Product Content Management and Content Management Platform. The Digital Experience Platform and Content Hub can both host structured content and publish the finalized version to Experience Edge. Both platforms offer different ways to manage content. During a technical and business evaluation, the evaluation panel must understand the difference between a Content Modelling focused approach, or a layout management focused approach. Sitecore Digital Experience Platform is also best not to be used to host many files and images in the Media Library. That responsibility should be offloaded to a digital asset management company like Sitecore Content Hub DAM. The technology evaluation panel must also understand how to work with a Headless CMS, where the HEAD needs to be hosted, and the costs associated with the HEAD. Composable DXP is fantastic, but everyone must understand the various cost components. Marketers and the data team will need to go into the CDP and Personalize the platform with an excellent understanding of how a composable "installation" works. All the Martech vendors have similar challenges that data and development teams need to work through with a full experience. Any CDP/analytics platform will, at some stage, require further data enrichment from other sources. Understanding the Sitecore Search features and limitations is also essential.
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.
Comprehensive Solution: Sitecore offers a fully integrated suite of products that cover the full spectrum of DXP capabilities, including search, personalization experimentation and more, delivering a complete composable DXP solution for customers.
Beyond Headless: XM Cloud provides more than just headless capabilities, featuring in-built tools like authoring host, page editor, etc., enabling faster and more powerful implementations.
Focus on AI: Sitecore has now got an excellent AI offering called Stream; it looks promising; however, it would be too early to give feedback on the same.
Customization: Sitecore's backend is highly customizable, allowing for deep modifications through pipelines and patch configurations.
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.
Experience Editor is a little old fashioned and sometimes slow to use.
Bulk operations in the Content Editor
Sitecore serialization is should be part of the Content Editor to provide visual reference for items which are serialized and will be overwritten by future deployments similar to what Unicorn does so well
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
Sitecore has proven that it can deliver on its promise of a robust, reliable enterprise CMS solution with plenty of features. Also, they keep updating it with more and better features. Now that we are highly trained on it we have started on getting the most out of it and we plan to keep doing more of that in the future.
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
Once you learn how to use the platform and can put a solid strategy in place to manage it long-term, it becomes a lot easier to use. The tricky part is working with resources who are familiar with the platform to navigate some of the common implementation and configuration pitfalls. Although Sitecore has worked very hard to overcome some of these from their earlier product versions by creating wizards and improving their support documentation, at the end of the day it is still a very complex and powerful system that needs to be implemented carefully in order to foster the best possible user experience for authors. So it could be rated very usable or not usable at all based on how much planning took place and the quality of the implementation.
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.
1. Customized software development & maintenance. 2. Technology Consulting - Consulting-based services for technology solutions data engineering or cloud solutions. 3. Used for tapping into multiple data sources such as CRM and marketing automation systems and, creating automated data extracts with a high-end visual representation of data. 4. Implemented for scheduling an existing report to automatically refresh and be delivered to specific users at a specific regular interval.
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.
Sitecore captures and remembers every single interaction your customers and prospects have in any part of the system, allowing you to build comprehensive, ever-learning profiles of each individual. From email marketing, to social media, to online shopping, Sitecore remembers where each interaction left off so you can automatically continue the conversation. Sitecore helps you manage your content for each and every experience your customers enjoy. Customize what content you want and the system will take care of how it's displayed.
Make sure you work with a partner that can help you take advantage of the entire platform. Specifically we see a lot of customers not taking advantage of Sitecore DMS and thus missing a huge opportunity. Sitecore is a platform that is meant to be constantly optimized and improved upon.
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.
Sitefinity is improving but at the time of decision making it had nothing that could compare with the A/B testing and personalisation features that Sitecore offers. This was a key differentiator and ultimately ensured Sitecore was purchased. WordPress isn't really comparable and isn't within our technology stack, which is mostly Microsoft.
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.
ROI depends on what features the customer wants to leverage from Sitecore. Sitecore is not just a CMS. It's CEP platform which comes with Analytics, Personalization, A/B Testing, and Email for marketers modules etc., out of the box.
Based on my experience some of the customers lean towards third party services. This is primarily due to lack of the understanding of these features. If a customer leverages these out of the box features ROI will be high. It depends on how much is being [sent] to third parties services.
Sitecore has very good accelerators in the market. These accelerators allows you to create response sites very quickly. If a simple campaign site takes 50K to build the site may save at least 50% of that cost. Examples of site accelerators are Brainjocks, Keystone, Cognifide etc.
