The Microsoft Azure App Service is a PaaS that enables users to build, deploy, and scale web apps and APIs, a fully managed service with built-in infrastructure maintenance, security patching, and scaling. Includes Azure Web Apps, Azure Mobile Apps, Azure API Apps, allowing developers to use popular frameworks including .NET, .NET Core, Java, Node.js, Python, PHP, and Ruby.
$9.49
per month
Progress Kendo UI
Score 8.0 out of 10
N/A
Kendo UI is a JavaScript UI toolkit that allows users to build responsive web-based apps integrated into their framework of choice (jQuery, Angular, React, or Vue). The vendor’s value proposition is that Kendo UI offers a large library of popular and configurable components ranging from sophisticated grids and charts to basic buttons, so users don’t have to waste development time building their UI. The vendor also says the large library of customizable themes means users can easily deploy a…
$999
per developer, royalty-free
Red Hat OpenShift
Score 9.2 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.
$0.08
per hour
Pricing
Azure App Service
Progress Kendo UI
Red Hat OpenShift
Editions & Modules
Shared Environment for dev/test
$9.49
per month
Basic Dedicated environment for dev/test
$54.75
per month
Standard Run production workloads
$73
per month
Premium Enhanced performance and scale
$146
per month
Kendo UI with Priority Support
$999
per developer, royalty-free
DevCraft UI
$1,299
per developer, royalty-free
DevCraft Complete
$1,499
per developer, royalty-free
DevCraft Ultimate
$2,199
per developer, royalty-free
No answers on this topic
Offerings
Pricing Offerings
Azure App Service
Progress Kendo UI
Red Hat OpenShift
Free Trial
Yes
Yes
Yes
Free/Freemium Version
No
No
Yes
Premium Consulting/Integration Services
No
Yes
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
Free and Shared (preview) plans are ideal for testing applications in a managed Azure environment. Basic, Standard and Premium plans are for production workloads and run on dedicated Virtual Machine instances. Each instance can support multiple applications and domains.
Kendo is more configurable. It has a great support base and community. It's well suited to integrate with ASP.NET MVC. It's well suited to integrate with AngularJS. You can create generic and dynamic controls which are configurable. With grids it provides higher …
We previously used DevExpress, and it was fine. We were embarking on a large project, and more people were familiar with Kendo than DevExpress, so we decided to standardize the platform with Kendo and move in that direction across all our work. It has been a fine …
Redhat has a high license cost but offers support and the ability to run workloads anywhere with practically no changes. Red hat allows easier shelling into a container to inspect what is wrong, VS ECS or EKS. There is a lengthy blog post on how to do that for ECS on AWSs blog. …
You may easily deploy your apps to Azure App Service if they were written in Visual Studio IDE (typically.NET applications). With a few clicks of the mouse, you may already deploy your application to a remote server using the Visual Studio IDE. As a result of the portal's bulk and complexity, I propose Heroku for less-experienced developers.
It allows us to extend the components or create new components in an easy way. The control suite is complete and powerful enough that you do not need to consider other competing packages. The controls are relatively easy to implement and when we ran into problems the documentation and online support were very reliable.
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.
Kendo UI controls provides rich set of features and capability that is required for enterprise products.
Performance of controls are satisfactory overall though few other vendors provides extraordinary performance for specific controls and for specific purpose. Kendo UI provides most of the required controls and with rich feature that made us to select Kendo UI controls for our development.
Kendo UI controls quality, in terms of performance, robustness and well defined interfaces are very positive notes.
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.
You may wind up putting a lot of eggs in one basket--not necessarily a con but something to keep in mind (most of your data will likely be managed and processed through Microsoft products/services if you fully commit to Azure App Service).
Learning new technology. If you're moving from on-premises to Azure App Service (or any cloud solutions), you'll likely have to rethink how things are done to achieve the same end results (and/or resources may become expensive quickly).
Kendo UI is always moving forward and staying current with latest development trends. While that is beneficial, that can cause some issues when supporting customers (particularly government) that don't move their IT infrastructure along nearly as fast. A prime example is web font icons. Great and easy to use, but where Kendo UI utilizes web font icons as the sole means of displaying an icon, not all organizations (again, especially government) allow the use of these. There have been times where Kendo UI became unusable and we had to downgrade to a version a few years old. Makes continued payment for licenses sometimes feel wasted as we may not be able to always use the new releases
Kendo UI has a wonderful feedback system and they do indeed listen to the community. However, there do seem to be some instances where there is large support for a new feature/component and it never gets addressed. It is easy to understand that not all ideas are easy or even prudent to implement, but would be nice to see a better follow-up on ideas with a current status
Refreshing Kendo UI grids is simple, yet the standard API method causes the grid to return to the default state. We have many use cases where we would love to update the grid data but need current grid state (such as expanded detail rows, sorts, filters, etc) preserved after the grid is updated so that users do not have to perform grid actions again to return to the desired state.
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.
Nothing better has come along. I'm always on the lookout for new UI libraries and I have tried most of them. Kendo has done a good job of keeping my business. They aren't perfect, but no one has done it better as far as I can tell. I'll keep a look out and my rating may change in the future if they get complacent.
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
I have given this rating because Azure App Service performs very well in terms of speed, reliability, and reducing overhead, and improves overall team productivity, with a little scope for improvement in complex testing scenarios and configurations, scalability concerns in a large setup, and similar tracking and audit needs.
it's easy to implement in applications. The kendo widgets are able to be used in almost any type of business application which has a UI. For most part, once the developer has completed a project which uses Kendo, many time code can be copy/paste into a new application. Kendo UI documentation keeps improving so finding the answers to questions can be easy
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.
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.
Microsoft has always been known for providing a high standard in terms of customer support and Azure App Service (and as a matter of fact the whole Azure Platform) is no exception. Azure App Service never caused us any issues and we only contacted their customer support for questions regarding server locations and pricing. I feel pretty satisfied with how they treat their customers.
Overall, we are satisfied with the support offered by the Progress Kendo UI team. We had raised few helpline incidents in the past and they have been resolved timely by the team. Also, we were satisfied with the level of information and support provided by the team.
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.
it took me about one day to make the components available for all the team members, including a quick demo, parallel setup in everyone’s workstation and packages deployment into our nuget server after 3 days of one to one support, everyone was able to use the components or find help in the documentation or resuest support
When we chose it, we did so because of its integration with Microsoft applications; now we need to integrate with AI, and Azure doesn't offer a good integration. That is the main reason to change it. It is still great to develop Windows- and Microsoft-based applications, but if we need to integrate with AI, Google wins by far.
At the time of our product selection we identified better cross-browser compatibility and we estimated that turnaround for support was superior. At the time, the vendor had a higher positive feedback footprint among their user community.
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.
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
Deployment of ASP.NET apps at the organization has been sped up.
An option to offer access to the version control system on a third platform so that we could easily deploy our apps.
Because of Azure App Service's scalability capabilities, the costs of running the services are kept to a minimum. As a result, we may save hundreds of dollars each month compared to the expenses of traditional servers by using fewer resources during slack periods.
Kendo UI has saved us a ton of time in development.
We were able to get certain things to market faster due to the fact that we didn't have to piece multiple libraries together like is so common with modern web development.
Because of the price of the library, however, we have not been able to purchase upgrades every year.
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.
