IBM Cloud Kubernetes Service is a
managed Kubernetes offering, delivering user tools and built-in security for rapid delivery of applications
that users can bind to cloud services related to IBM Watson®, IoT, DevOps
and data analytics. As a certified K8s provider, IBM Cloud Kubernetes
Service provides intelligent scheduling, self-healing, horizontal
scaling, service discovery and load balancing, automated rollouts and
rollbacks, and secret and configuration management. The Kubernetes…
N/A
IBM WebSphere Hybrid Edition
Score 8.1 out of 10
N/A
WebSphere Hybrid Edition from IBM is a collection of WebSphere application runtimes and modernization tools that provides support for on-premise and major public cloud deployments, in virtual machines, containers and Kubernetes. The user can choose any WebSphere edition and deploy Liberty and application modernization tools to help move to a cloud-native architecture, modernize existing applications and support an existing WebSphere estate.
IBM Cloud Kubernetes Service is ideal for deploying modern applications on a microservices architecture -- where easy scaling and ability to update are important. IBM Cloud Kubernetes Service also handles automated deployments and load balancing very well, particularly if you're already working in the IBM Cloud ecosystem. There are applications less suited to IBM Cloud Kubernetes Service -- such as very small applications, where managing an IBM Cloud Kubernetes Service cluster would be overkill. Also, users not familiar with container organization might find IBM Cloud Kubernetes Service to be a challenge to manage effectively.
IBM WebSphere Hybrid edition is well-suited for the development and deployment of large enterprise-level applications such as Electronic Health Records that are used in our organization. IBM WebSphere is appropriate for organizations that require strong security and compliance as it provides a high level of security and compliance features. This works well with organizations that are subject to strict regulatory requirements, such as hospitals.
IBM has a strong focus on serverless and Kubernetes. This shows in the platform. Deploying containers to Kubernetes was very easy.
Deploying a Kubernetes cluster through the GUI is very easy and quick. On top of that, IBM Cloud offers a single node cluster for Free.
Container Registry is a very good product for managing container images. Integration with Kubernetes was seemless.
Portability. To transition from Google Cloud Kubernetes to IBM Cloud Kubernetes took almost no effort. We mostly use the CLI and the standard tools such as kubectl were present.
I constantly get this error even when everything is well configured prefect.exceptions.AuthorizationError: [{'path': ['auth_info'], 'message': 'AuthenticationError: Forbidden', 'extensions': {'code': 'UNAUTHENTICATED'}}]
Then sometimes the error disapear without changine anything, happened twice to me. Should there be an issue with the authentication service? Please let's improve or let users know why this may be happening.
Improve the UX in the browse console when removing many images at once
UX on the process of installing KeyCloack operator
Ease of use in terms of deployment, give simple interface to do simple stuff like Tomcat, JBoss or GlassFish.
Takes long time to start the server.
The Liferay wars need to be decorated and then deployed. Perhaps we could simplify that.
Some of the concepts are good for complexity that WAS can handle but could be simplified and better documented, like concepts of well and profile, context, etc.
A Liferay war file created using Liferay Developer studio runs fine in Tomcat, however that may not run in WAS 7.x because it needs to be decorated. I had one war for a Liferay portlet with a simple cron job, and had hard time running to WAS server. It was running on the latest free download done on my friends m/c. Other times I have seen that there are issues running a war file that runs on Tomcat but runs on WAS after lot of customization for WAS.
The corporations like this however, the product may need better vibrant community of users where issues can be discussed.
We have our application running on a CentOS compartment on IBM Cloud Kubernetes Service. We have been utilizing the help since IBM Cloud initially dispatched. We liked the adaptability and versatility that IBM Cloud Kubernetes Service give us. Since we are tiny, the Kubernetes administration is just utilized at present inside my venture bunch.
Mostly we will be renewing unless the strategic direction changes drastically or there are other complelling external circumstances. We've been on a multi year project to modernize our legacy applications and that effort will continue for the foreseeable future.
We actually haven't had any real problems in our clusters recently and the results we have gotten from adopting IBM Cloud Kubernetes Service have been beyond even our greatest expectations. The community has helped optimize the use of the system and make it relatively simpler to use.
WebSphere Application Server is used across our organization. Most projects use this for Java products and applications. Being robust and scalable makes it even more usable. We love using WebSphere Application Server due to its configuration management ability made simple and vast across all java related parameters. It is dependent on the features and upgrades and IBM releases some great upgrades to WebSphere Application Server.
The self-guided support was solid, and there are plenty of online videos to guide first time users, but I think one area of improvement is a faster way to transfer a large quantity of files from our local machine to the cloud for storage (Aspera)
IBM was quick to respond when we had an issue with our specific infrastructure. We raised a PMR, which they picked up quickly and updated us about every step of the way. We had an appropriate fix for quite a business critical issue within a fortnight, which was impressive!
Online training is really an important resource for using these tools. IBM's help center is rich in useful information and tips. Also, external guides and tutorials are available (e.g. on youtube), but I followed only IBM ones and I had no difficulties.
Ease of use. Very intuitive. We have been looking for a product that allows us to orchestrate our docker containers in a way where it allows us to effectively scale our applications to production. It also provides us a way of monitoring all our infrastructure in a very clear concise way.
The IBM Cloud Kubernetes Service is quite flexible platform with profitable Cloud functions performance and the data security through IBM Cloud Kubernetes Service is nice. To manage container easily and process huge amount of data at the same time, the IBM Cloud Kubernetes Service is amazing ad the platform deployment is very easy after training.
Cleo Integration Clould has many bells and whistles; however, when we added more maps and trading partners, it really slowed down. We found that the Cleo support was very slow to respond and there was a language barrier. IBM Websphere had better customer support and its processing was much faster than Cleo Integration Cloud
IBM's CKS does not offers automatic autoscaling nor vertical scaling (automatic). Other services like Google Kubernetes Engine scales up and down very well
IKS can provide around 30% savings when it comes to operational costs since Kubernetes is designed to run applications in most machines in the most efficient manner possible.
Managed Kubernetes can save a company time by 45% since Managed Kubernetes usually is seamlessly updated, without any interruptions with the workload. IKS fall into this benefit.
We heard people had saved in maintenance downtimes when it comes to Kubernetes by a factor of 10 so IKS can contribute to more flexible and distributed services with virtually no downtime.
Continuous uptime of the business applications we manage
It's now much simpler for me to build and deploy cloud-native applications.
Because it can offload for me management and maintenance of the application server to IBM I can focus on the development, deployment and testing of the applications which is more important
