Menu

1 / 4

Cloud Run vs GKE: Picking a Home for Your Containers

DEV Community: kubernetes·Vishwa·about 13 hours ago
#JCbSRk5w
#devtokubernetes#devto#dev#cloud#load
Reading 0:00
15s threshold

A small API with spiky traffic and a 20-service platform need different things

Imagine two teams. One has a small product API that is quiet at 3 am and busy at lunch. The other runs about 20 microservices for checkout, payments and orders, with steady traffic all day and strict rules about which service can talk to which. Both have Docker images ready. Where should each one run?

The problem

The same container can run on Cloud Run or on GKE (Google Kubernetes Engine). Picking the wrong one hurts in a predictable way:

Put the small spiky API on GKE, and you pay for node VMs that sit idle at night, and someone has to look after a cluster.

Put a large, tightly networked platform on Cloud Run, and you can end up fighting for control you do not have: sidecars, pod-level network rules, node pools tuned for a sale.

The choice is not about which tool is better. It is about traffic pattern and how much control you need.

The solution: choose by traffic and control

Cloud Run is serverless.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.