Architecture decision guides for Kailash SDK including framework selection (Core SDK vs DataFlow vs Nexus vs Kaizen), runtime selection (Async vs Sync), database selection (PostgreSQL vs SQLite), node selection, and test tier selection. Use when asking about 'which framework', 'choose framework', 'which runtime', 'which database', 'which node', 'architecture decision', 'when to use', 'Core SDK vs DataFlow', 'PostgreSQL vs SQLite', 'AsyncLocalRuntime vs LocalRuntime', or 'test tier selection'.
Instalación
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Architecture decision guides for Kailash SDK including framework selection (Core SDK vs DataFlow vs Nexus vs Kaizen), runtime selection (Async vs Sync), database selection (PostgreSQL vs SQLite), node selection, and test tier selection. Use when asking about 'which framework', 'choose framework', 'which runtime', 'which database', 'which node', 'architecture decision', 'when to use', 'Core SDK vs DataFlow', 'PostgreSQL vs SQLite', 'AsyncLocalRuntime vs LocalRuntime', or 'test tier selection'.
Kailash Architecture Decisions
Decision guides for selecting the right frameworks, runtimes, databases, nodes, and testing strategies.
Unit (fast), Integration (real infra), E2E (full system)
Framework Selection Matrix
Need
Framework
Why
Custom workflows
Core SDK
Full control, 140+ nodes
Database CRUD
DataFlow
Auto-generated nodes
Multi-channel API
Nexus
API + CLI + MCP instantly
AI agents
Kaizen
Signature-based agents
All of above
Combine them
They work together
Runtime Selection Flow
Deploying to Docker/async/Kubernetes?
YES -> AsyncLocalRuntime (async-first, no threads)
NO -> CLI/script?
YES -> LocalRuntime (sync execution)
NO -> Use get_runtime() for auto-detection
Database Selection Flow
Production deployment? -> PostgreSQL (scalable, enterprise)
Development/testing? -> SQLite (simple, fast setup)
High concurrency? -> PostgreSQL (better concurrency)
