architecture-decisions

To choose the right Kailash framework, map your project's primary requirements against the decision matrices for Core SDK, DataFlow, Nexus, and Kaizen. This process compares each framework's capabilities to match your specific deployment, workflow, and data processing needs.

Use LocalRuntime or AsyncLocalRuntime based on your specific deployment and execution context. The runtime selection process evaluates your data-concurrency needs and deployment environment to determine which execution model provides the optimal performance for your Kailash application.

The best way to select a database for a Kailash application is to evaluate your data-concurrency needs and deployment context. The architecture decision process compares PostgreSQL and SQLite to determine which database choice aligns with your project's scale and workflow requirements.

Yes, Kailash architecture planning supports migrations by applying decision matrices to map existing system requirements to new builds. This process helps you select the optimal framework, runtime, database, node, and test tier for your migration scenario with consistent guardrails.

Determine the right test tier for a Kailash workflow by evaluating your testing scope against unit, integration, and end-to-end options. The architecture decision process maps your testing requirements to select the appropriate test tier with consistent guardrails.

Node selection matters because it matches task-specific requirements to the appropriate execution components. The architecture decision process maps your workflow tasks to specific nodes, ensuring optimal performance and compatibility within your chosen Kailash framework and runtime.