The Adobe Experience Platform is a platform-as-a-service (PaaS) serving as the foundation of the Adobe Experience Cloud, and is provided as a customer experience management platform with real-time customer profiles, continuous intelligence, and an open and extensible architecture that enables delivering personalized experiences at scale.
N/A
Red Hat OpenShift
Score 8.8 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.
The Adobe Experience Platform is well suited for companies that are maturing or have matured in their digital offerings and are looking for very sophisticated tools to elevate to the next level. It's also for well resourced teams, both financially and head count to take advantage of the deep functionality and integrations.
I've seen multiple universities that have quite investments in Red Hat enterprise virtualization. They don't want to go with the VMware route due to the expense. So Red Hat OpenShift virtualization is a natural fit for them in that environment. I've also seen a lot of VMware customers that are not able financially to sustain the cost increases with the product. So they're looking for an alternative. And Red Hat OpenShift virtualization fills that need.
One thing is the way how it works with the GitHubs model on an enterprise business, how the hub and spoke topology works. Hub cluster topology works the way how there is a governance model to enforce policies. The R back models, the Red Hat OpenShift virtualization that supports the cube board and developer workspace is one big feature within. So yes, these are all some features I would call out.
So I don't know that this is a specific disadvantage for Red Hat OpenShift. It's a challenge for anything that Kubernetes face is. There's an extremely large learning curve associated with it and once you get to the point where you're comfortable with it, it's really not bad. But beating that learning curve is a challenge. I've done a couple presentations on our implementation of Red Hat OpenShift at various conferences and one of the slides I always have in there is a tweet from years ago that said, "I tried to teach somebody Kubernetes once. Now neither of us knows what it is."
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
Overall I really like the Adobe Experience Cloud after a couple years of figuring out various tools. They are extremely powerful. The time commitment to learn them is high since it's not a tool you can easily begin using without much training.
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
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.
Openshift performance is based on the underlying infrastructure, the K8s design, and the applications' design. Cloud-native applications should have resilience baked in and should not depend on infrastructure resilience. Standard stateful apps may still depend on the underlying infrastructure. It depends on the approach.
Adobe has support at all levels and for each product but beyond tool questions you'll often be told they can help but it requires some paid consulting hours. So you either hire Adobe consultants or find 3rd part consultants who know their products well.
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
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.
In most cases we have found Adobe products to be harder to use but offer a lot more capabilities. In some cases Adobe products are missing key, basic functions. Adobe does offer a more holistic toolset rather than buying pieces of the puzzle and having to integrate on your own but that results in paying for a higher price tag.
Our developer community is using Red Hat OpenShift for years and they are familiar and comfortable with the product. Red Hat OpenShift UI makes it easier for new developers to adopt without knowing much of Kubernetes. Our platform team feels it’s easy to mange the cluster and upgrades. Other options has more operation overhead and less friendly to developers not have in-depth knowledge of Kubernetes.
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
