architecture-decisions

Name: architecture-decisions
Availability: InStock
Author: Dchuuuuuu

Guides framework, runtime, database, node, and test tier selection for Kailash SDK projects.

Updated Apr 2, 2026

Search Tags:#decision guide #architecture decisions #kailash sdk #framework selection #database selection #runtime selection #test tiers

Ready to run

npx skills add https://github.com/Dchuuuuuu/disease-risk-classifier --skill architecture-decisions-dchuuuuuu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture-decisions
Source: https://github.com/Dchuuuuuu/disease-risk-classifier/tree/main/.claude/skills/13-architecture-decisions
Command: npx skills add https://github.com/Dchuuuuuu/disease-risk-classifier --skill architecture-decisions-dchuuuuuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing between Core SDK, DataFlow, Nexus, and Kaizen—or between runtimes, databases, nodes, and test tiers—requires institutional knowledge that developers often lack, leading to wrong architectural choices like using LocalRuntime in Docker or SQLite in production. ## Core Features & Use Cases - Framework Selection: Decision matrices and flowcharts for choosing Core SDK, DataFlow, Nexus, Kaizen, or combinations, with code examples for each. - Runtime & Database Decisions: Rules for AsyncLocalRuntime vs LocalRuntime based on deployment context, and PostgreSQL vs SQLite based on environment. - Node & Test Tier Selection: Guidance for picking from 110+ nodes and choosing unit, integration, or E2E test tiers. - Use Case: When starting a new database-backed API project, consult this skill to decide on DataFlow + Nexus with AsyncLocalRuntime and PostgreSQL before writing any code. ## Quick Start Ask which Kailash framework and runtime to use for a Docker-deployed database application with API access.

Frequently Asked Questions about architecture-decisions

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I choose between Core SDK, DataFlow, Nexus, and Kaizen?▼

Choose Core SDK for custom workflows with fine-grained control, DataFlow for database operations with auto-generated CRUD nodes, Nexus for multi-channel API/CLI/MCP platforms, and Kaizen for AI agent systems. The frameworks are built on Core SDK and can be combined.

Should I use LocalRuntime or AsyncLocalRuntime?▼

Use AsyncLocalRuntime for Docker, FastAPI, and high-concurrency production deployments, and LocalRuntime for CLI scripts and synchronous tests. When unsure, call get_runtime() for automatic context-based detection.

PostgreSQL vs SQLite for a Kailash DataFlow application?▼

Use PostgreSQL for production deployments and high-concurrency workloads, and SQLite for development and testing where fast setup matters. Never use SQLite for production high-concurrency scenarios.

Can I combine multiple Kailash frameworks in one project?▼

Yes, frameworks stack on Core SDK and work together. Common combinations include DataFlow + Nexus for multi-channel database apps and Core SDK + Kaizen for AI-powered custom workflows.

What happens if I use LocalRuntime inside Docker?▼

Using LocalRuntime in Docker causes hangs due to its threading model. Docker and FastAPI deployments require AsyncLocalRuntime, which uses async/await without threads and runs 10-100x faster.

How do I decide between unit, integration, and E2E test tiers?▼

Use Tier 1 unit tests for individual functions with mocking allowed, Tier 2 integration tests for workflow execution against real infrastructure, and Tier 3 E2E tests for complete user flows. Most projects use all three tiers.