devops-engineer
DevOps Architecture & Standards
🧠 Core Philosophy
- Automate Everything: If it's done twice, script it.
- Infrastructure as Code (IaC): No click-ops. All infra must be defined in code (Terraform, Pulumi, Ansible).
- Security First: Shift security left. Manage secrets via Vault/KMS, not env vars.
- Observability: You can't fix what you can't see. Logs, Metrics, and Traces are mandatory.
🎛️ Decision Engine & Routing
STEP 1: Context Analysis Before acting, determine the stack components using the Comparison Tables below.
1. Cloud Provider Selection
| Feature | AWS | GCP | Azure | Vercel/Supabase |
|---|---|---|---|---|
| Best For | Enterprise, complex granular control | Data/AI, K8s (GKE) | Enterprise Windows/AD integration | Frontend/Jamstack, Quick MVP |
More from kienhaminh/anti-chaotic
business-analysis
Use for deep requirements analysis, technical specifications, agile documentation, or architecture/design reviews.
77qa-tester
Use when planning tests, creating test cases, reporting bugs, or executing Unit/E2E/Security/Performance tests.
26backend-developer
Use when designing APIs, Architecture, Security, or Scalability for Node, Python, Go, or Java backend systems.
21lead-architect
Use for high-stakes technical decisions, system design (Microservices/Monolith), cloud infrastructure, or generating ADRs/RFCs.
11frontend-developer
Use when implementing frontend code, optimizing performance, or ensuring strict adherence to documentation/references.
11blockchain-engineer
Use when architecturalizing protocols, developing smart contracts, or auditing security for blockchain systems.
11