architecture-decisions

Name: architecture-decisions
Availability: InStock
Author: ssssssssassssss

Select Kailash architecture components across framework, runtime, database, and node decisions.

Updated Apr 2, 2026

Search Tags:#architecture #database #patterns #runtime #decision-making #framework-selection #node-selection

Ready to run

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

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture decision guides for Kailash SDK including framework selection (Core SDK vs DataFlow vs Nexus vs Kaizen), runtime selection, database choice, node selection, and test-tier decisions. Use when designing or evolving a Kailash-based system to pick optimal configurations.

Core Features & Use Cases

Framework selection guidance for Core SDK, DataFlow, Nexus, and Kaizen.
Runtime selection guidance for AsyncLocalRuntime vs LocalRuntime.
Database and node decision patterns for Postgres/SQLite and various task paths.
Quick reference decision matrices and practical examples for enterprise-scale decisions.

Quick Start

Start by selecting the framework (Core SDK, DataFlow, Nexus, or Kaizen) and then follow the runtime, database, and node guidance to finalize an architecture plan.

Frequently Asked Questions about architecture-decisions

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

FAQPage Schema

How do I choose the right Kailash framework for my project architecture?▼

Kailash framework selection depends on matching project requirements to Core SDK, DataFlow, Nexus, or Kaizen capabilities. Decision matrices evaluate framework features against use cases, providing reference patterns and implementation guidance to finalize an optimal architecture plan.

What is the difference between AsyncLocalRuntime and LocalRuntime in Kailash?▼

AsyncLocalRuntime and LocalRuntime differ in execution model for Kailash workflows. Runtime selection guidance evaluates concurrency requirements and task characteristics to determine which runtime optimally handles the project's execution patterns and throughput needs.

When should I use Postgres vs SQLite for Kailash database decisions?▼

Postgres vs SQLite selection for Kailash depends on scale, deployment context, and data management requirements. Database decision patterns evaluate enterprise-scale needs, transaction complexity, and operational constraints to recommend the appropriate database configuration for your architecture.

Can I use Kailash architecture decisions for enterprise-scale systems?▼

Kailash architecture decisions support enterprise-scale systems through decision matrices, reference patterns, and practical examples. Framework, runtime, database, and node selection guidance addresses complex requirements across Core SDK, DataFlow, Nexus, and Kaizen for large deployments.

What's the best way to select nodes for Kailash task paths?▼

Node selection in Kailash follows decision patterns that match task path requirements to appropriate node types. Guidance evaluates task complexity, data flow needs, and framework alignment to recommend optimal node configurations within your chosen architecture.

How do I plan test-tier decisions in a Kailash-based architecture?▼

Test-tier decisions in Kailash architecture use decision matrices to determine appropriate testing levels across framework components. Guidance aligns test tiers with selected runtime, database, and node configurations to ensure coverage matches enterprise-scale implementation requirements.