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
OutSystems
Score 6.4 out of 10
N/A
The OutSystems Platform is a Platform-as-a-Service solution for rapid delivery of responsive web and mobile applications. It includes functionalities required to develop, deploy, manage and change web and mobile applications. It is targeted at the delivery of enterprise applications that require integration with backend systems, complex business rules and logic, usable interfaces and flexibility to change. It can be deployed in the cloud, on-premises or in hybrid environments.
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.
Well suited for internal exposure of business processes (invoicing, API layer to other systems, customer maintenance etc), whether a UI is required or not. Not so well suited for full fledged web design. An OutSystems application must serve one particular business need, if gets too much functionalities and responsibilities it tends to get chaotic and complex.
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.
OpenShift virtualization has a little room for improvement. I'm coming from it as a Rev customer. There's some things in that OpenShift virtualization that were in Rev that I would like to see in OpenShift virtualization. I realized that they're chasing the VMware crowd and that's fine, but from us old Rev customers, we'd like to see some things that was in Rev around via migration and things of that nature that could be in OpenShift virtualization, I hope is being planned to be put in.
Price – The licensing model of OutSystems is very expensive and not suitable for small scale developments. This is offset by the time to develop and stability for larger scale developments
Flexibility on PaaS version – The PaaS hosted version of OutSystems limits your flexibility to access the front end and backend database systems which can significantly restrict your options on high data volume developments or where anything requiring slightly out of the ordinary access is required
Same price for PaaS and self-hosted system. Licensing model dictates that you pay the same price even when you host the system on your own hardware which effectively means you pay more to manage the infrastructure yourself
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
We are very happy with OutSystems and our developers deliver good work. OutSystems lets us build new software on a regulare (2 weekly) basis, which is highly flexible and adjustable. Even without very much experience, our developers manage to build usefull software, which is working a lot better than our previous (legacy) software.
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
OutSystems has a feature in which we can develop a functionality in a application and can use that functionality in another application without developing it again. That is main plus point for the development team so they can work with different functionalities rather focusing on the same thing again and again. if we want to make any change on the user side then we can make it live with just the deployment using the service center.
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
The tech support is very reachable. Usually by [email] from but also by phone if needed. We had some difficulties at the start with understanding "what our machine was doing" under high performance load. After some good sessions understanding our needs they delivered good solutions for our problems we had in the beginning.
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 online training material is well designed and explanations are step by step, helping trainees to understand and follow each exercise and new concept.
In a large company, patiently and consistently work the behind the scenes politics with business and IT partners across the firm. This is transformational - you will need a solid set of key business partners to lock arms together to move forward.
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.
I tried to use WordPress with some success. Also looked at Joomla. But when I saw OutSystems I knew I had been wasting my time there. It takes you longer to get going with OutSystems - but even I as a novice realized immediately that Outsystems is simply in another league. Outsystems is powerful. (Can you compare WordPress and Joomla to Outsystems - I don't think so).
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.
The ease of use of the OutSystems development process has been the biggest ROI for us. We have developed our Framework product and maintained/enhanced it with only 4 workers.
OutSystems has enhanced their product very significantly over the last 4 years. They have gone from a simple to use tool to a very simple to use sophisticated tool that covers the standard mainframe-based computing apps and the apps used on handheld mobile devices all using the same basic set of development tools.
