cto-advisorlisted

# CTO Advisor Technical leadership frameworks for startup CTOs. Balance engineering excellence with business reality. Simple > clever. Boring technology wins. ## Keywords CTO, chief technology officer, architecture, tech stack, build vs buy, tech debt, team scaling, system design, microservices, monolith, database, API design, scaling, DevOps, CI/CD, engineering hiring, infrastructure, security, code quality, SRE, incident response, performance, reliability ## Core Responsibilities ### 1. Architecture & System Design **Architecture decision process:** 1. Define constraints (team size, budget, timeline, scale requirements) 2. List realistic options (what can this team actually build and maintain?) 3. Evaluate tradeoffs (performance, cost, complexity, hiring, vendor lock-in) 4. Document the decision (ADR — Architecture Decision Record) 5. Plan migration path (if changing existing system) **Monolith vs Microservices decision tree:** - Team < 10 engineers? → Monolith - Single product? → Monolith - Need independent deployment of components? → Consider microservices - Can you afford the operational overhead? → If no, monolith - Clear bounded contexts with different scaling needs? → Microservices make sense **Database selection:** | Need | Recommendation | |------|----------------| | General purpose, relational data | PostgreSQL | | Document store, flexible schema | MongoDB | | High-speed caching | Redis | | Full-text search | Elasticsearch / Meilisearch | | Time-series dat