Google Cloud Run vs. IBM Cloud Kubernetes Service

Microservices and RestFul API application as it is fast and reliant. Seamless integration with event triggers such as pubsub or event arc, so you can easily integrate that with usecases with file uploads, database changes, etc. Basically great with short-lived tasks, if however, you have long-running processses, Cloud Run might not be idle for this. For example if you have a long running data processing task, other solutions such as kubeflow pipelines or dataflow are more suited for this kind of tasks. Cloud Run is also stateless, so if you need memory, you will have to connect an external database.

Incentivized

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.

Incentivized

• Real-time autoscaling. Escalamento automático em tempo real
• Simplified Continuous Deployment. Implantação contínua simplificada
• Running tasks in the background. Execução de tarefas em segundo plano

Incentivized

• 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.

Incentivized

• Cloud Run doesn't allow you to redeploy an already existing revision which can be inconvenient in some use cases
• Tricky to get the deployment working to start but once it's working that's great
• The actual deployment is not the fastest but it's not too bad

Incentivized

• 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

Incentivized

We definitely need to renew it because we dont own our own infrastructure and storage and we are happy with Cloud Run features

Incentivized

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.

Incentivized

The UI/console is great... the documentation is top-notch for developers, but the CLI itself when you have to script around it is very complex and easy to forget some options... the downside of a generic command line client.

Incentivized

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.

Incentivized

Not seen any major issues when we run applications its good

Incentivized

IBM's cloud is almost infallible.

Incentivized

Initially we felt slow but slowly it picked up and easy to manage

Incentivized

IBM's cloud has a site in my conuntry (MEXICO) so the network latency was almost 0

Incentivized

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)

Incentivized

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.

Incentivized

I was involved in the initial implementation setup, Its easy with the given documentaiton we can do ourself. Not that critical

Incentivized

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.

Incentivized

AWS Lambda supports code zip package, enabling lower cold start time. Also, AWS Lambda pricing is much simpler, easier to understand.

Other than that, the 2 products are very similar, including the Docker image support: the image must be built based on proprietary base image.

Obviously, if your other services are running in GCP, then Google Cloud Run is your only choice for tight integration, & private networking.

Incentivized

I have earlier used various services, such as Kubernetes and Google Cloud Run. Still, IBM Cloud Kubernetes Service offers more convenience and a larger set of functions and features are available in Kubernetes. Google Cloud Run is much closer to a server less approach to deployment, although it gives slightly less flexibility in terms of configuration than IBM Cloud Kubernetes Service.

It has good auto scale feature and reliable also

Incentivized

IBM's CKS does not offers automatic autoscaling nor vertical scaling (automatic). Other services like Google Kubernetes Engine scales up and down very well

Incentivized

• It has saved us some costs since we now do not require a live server and have moved to a serverless workflow for these services
• Breaking changes do not affect the entire application now that we have separated our concerns using a serverless service
• Much easier to debug since we can now isolate our services and reduce the search space for finding/fixing bugs

Incentivized

• 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.

Incentivized