Likelihood to Recommend [Mirantis Cloud Native Suite (Docker Enterprise)] is the most advanced tool till now, which works as a VMs and separates any single application from the dependencies. Also, this tool is helping me in the agile development of the processes. It is strongly recommended to almost all major organizations.
Read full review 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.
Read full review Pros Containers - Docker is the go-to when using Containers, which are super useful if you need an environment that works both for Windows and Linux Efficiency - Docker is very lightweight and doesn't demand too much from your CPU or server CI/CD - Docker is excellent for plumbing into your build pipeline. It integrates nicely, is reliable, and has an easy set up. Read full review 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. Read full review Cons Containers are often opaque - if a container doesn't work out of the box, it's messy to fix. Logging is complexified by the multiple containers and logs are often not piped to places you expect them to be. Networking is complexified due to internal port mapping between containers, etc. Read full review 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." Read full review Likelihood to Renew Leverage OpenShift Online constantly at both the free and paid tiers. While AWS is convenient, it often brings more administration than I want to deal with for a quick application (i.e. Drupal or Wordpress blog). OpenShift also simplifies the DNS registration and ability to share application environments with team members
Read full review Usability Docker's CLI has a lot of options, and they aren't all intuitive. And there are so many tools in the space (Docker Compose, Docker Swarm, etc) that have their own configuration as well. So while there is a lot to learn, most concepts transfer easily and can be learned once and applied across everything.
Read full review 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
Read full review Performance 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.
Read full review Support Rating The community support for Docker is fantastic. There is almost always an answer for any issue I might encounter day-to-day, either on Stack Overflow, a helpful blog post, or the community Slack workspace. I've never come across a problem that I was unable to solve via some searching around in the community.
Read full review 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
Read full review Alternatives Considered We've used XAMPP, PHPmyAdmin and similar local environments (our app is on PHP). Because of how easy you can change the configuration of libraries on PHP and versions (which is SO painful on XAMPP or other friendly LAMP local servers) we are using Docker right now. Also, being sure that the environment is exactly the same makes things easier for developing.
Read full review 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 .
Read full review Contract Terms and Pricing Model 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.
Read full review Return on Investment Docker has made it possible for us to deploy code faster, increasing the productivity of our development teams. Docker has made it possible for us to decentralize our build and release system. This means that teams can deploy on their own schedule and our dev ops team can concentrate on building better tools rather than deploying for the teams Docker has allowed us to virtualize our entire development process and made it much simpler to build out new data centers. This, in turn, is significantly increasing our ROI by providing a path forward for internationalization. Read full review Positive: Reduction in physical and virtual machine footprint Negative: Lack of native end to end o11y has caused a great deal of focus from our enterprise monitoring folks Positive: OCP has allowed developers to have a quick and easy space to experiment Read full review ScreenShots