Kubernetes Is Overkill for 99% of Apps

The Kubernetes Tax

The article highlights the unnecessary complexity of using Kubernetes for most applications, citing the example of Logtide, which runs 500,000 logs/day on Docker Compose with 99.8% uptime. The author argues that Kubernetes has a massive complexity tax, including a steep learning curve, operational overhead, and significant infrastructure costs.

Why This Matters

The technical reality is that most applications do not require the complexity of Kubernetes, and the ideal model of simplicity and scalability can be achieved with simpler tools like Docker Compose. The failure to recognize this can result in significant costs, with a recent case study showing a team spending 60 hours per month on Kubernetes operations, equivalent to 1.5 engineer months.

Key Insights

• Logtide handles 500,000 logs/day on a single server with Docker Compose: [Logtide Blog, 2026]
• Docker Compose can be used for production workloads with proper configuration and monitoring: [Docker Documentation, 2022]
• Kubernetes is often overkill for small to medium-sized applications, with 80% of users being at companies with 1000+ employees: [CNCF Survey, 2025]

Working Example

version: '3.8'
services:
  postgres:
    image: timescale/timescaledb:latest-pg16
    volumes:
      - postgres_data:/var/lib/postgresql/data
    environment:
      POSTGRES_DB: logtide
      POSTGRES_USER: logtide
      POSTGRES_PASSWORD: ${DB_PASSWORD}
    deploy:
      resources:
        limits:
          memory: 4G

Practical Applications

• Use Case: Logtide uses Docker Compose for its production workload, handling 500,000 logs/day with 99.8% uptime.
• Pitfall: Using Kubernetes for small applications can result in unnecessary complexity and costs, diverting resources away from core development.

References:

• https://dev.to/polliog/kubernetes-is-overkill-for-99-of-apps-we-run-500k-logsday-on-docker-compose-2ode
• https://github.com/logtide-dev/logtide
• https://logtide.dev