What are the trade-offs between serverless and Kubernetes?

Serverless (Lambda) vs. Kubernetes (EKS/GKE) trade-offs: Serverless advantages: zero infrastructure management, scale-to-zero (no idle cost), automatic scaling to millions of invocations, faster deployment cycles, built-in HA, no capacity planning. Kubernetes advantages: run any workload (long-running processes, stateful apps, databases), full control over networking/scheduling/resource allocation, no execution time limits, consistent latency (no cold starts with pre-provisioned pods), multi-cloud portability via CNCF standards, better GPU workload support, run custom runtimes/sidecar patterns. When to choose serverless: event-driven processing, variable/unpredictable traffic, rapid prototyping, cost optimization for low-traffic apps. When to choose Kubernetes: consistent high-traffic workloads (cost breaks even ~3M+ Lambda invocations/month), long-running processes, complex networking requirements, existing containerized workloads. Hybrid approach: use Lambda for event processing and async jobs, Kubernetes for customer-facing APIs with predictable traffic. AWS Fargate bridges both worlds: serverless container execution without K8s cluster management.