Axway's Amplify is a universal API management platform that unifies what tools are already in place to get digital products where they can be seen and used. Users can publish, validate, and govern APIs.
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.
It's a great application to backup your data automatically to the cloud and then access later. The automatic restore of certain folders is handy and one less thing to worry about when you're setting up a new PC again. I haven't really encountered any issues with Syncplicity to have any thoughts where it could be improved or where it wouldn't work.
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.
By default, it is setup to backup my Desktop Shortcuts, My Documents, and my Internet Explorer Favorites folders. When I sign into a new PC, it automatically syncs these items, making it easy for my data to travel with me.
I'm able to easily share my items/folders with coworkers, granting them read or read/write access as required.
I like that items that are shared with me allow me to choose to sync them to my PC or not. This allows me to sync smaller items like documents and spreadsheets, but keep things like webex recordings stored in the cloud and not using up gigabtyes of space on my PC. :)
I like that, during times when I want to free up resources, I can pause the syncing of files.
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.
I would appreciate it if it backed up more than just Desktop, Favorites and Documents by default. I'm not sure if this was something chosen by my employer, but it would be nice if the whole profile folder was backed up by default, so my pictures, music, and videos folders were included.
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."
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
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.
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.
I use CrashPlan for my personal PC at home. I think both products have their pluses and minuses. Both products allow you to backup your selected data to the cloud. CrashPlan doesn't easily allow for file sharing (CrashPlan isn't really a collaboration tool as much as it is a backup tool). Both products have easy restore options. However Syncplicity automatically restoring certain data when syncing with a new PC is very handy and a feature that CrashPlan doesn't offer
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
