deploying-applicationslisted

# Deploying Applications Production deployment patterns from Kubernetes to serverless and edge functions. Bridges the gap from application assembly to production infrastructure. ## Purpose This skill provides clear guidance for: - Selecting the right deployment strategy (Kubernetes, serverless, containers, edge) - Implementing Infrastructure as Code with Pulumi or OpenTofu - Setting up GitOps automation with ArgoCD or Flux - Choosing serverless databases (Neon, Turso, PlanetScale) - Deploying edge functions (Cloudflare Workers, Deno Deploy) ## When to Use This Skill Use this skill when: - Deploying applications to production infrastructure - Setting up CI/CD pipelines and GitOps workflows - Choosing between Kubernetes, serverless, or edge deployment - Implementing Infrastructure as Code (Pulumi, OpenTofu, SST) - Migrating from manual deployment to automated infrastructure - Integrating with `assembling-components` for complete deployment flow ## Deployment Strategy Decision Tree ``` WORKLOAD TYPE? ├── COMPLEX MICROSERVICES (10+ services) │ └─ Kubernetes + ArgoCD/Flux (GitOps) │ ├─ Helm 4.0 for packaging │ ├─ Service mesh: Linkerd (5-10% overhead) or Istio (25-35%) │ └─ See references/kubernetes-patterns.md ├── VARIABLE TRAFFIC / COST-SENSITIVE │ └─ Serverless │ ├─ Database: Neon/Turso (scale-to-zero) │ ├─ Compute: Vercel, AWS Lambda, Cloud Functions │ ├─ Edge: Cloudflare Workers (<5ms cold start) │ └─ See references/serve