architecture-decisions

To choose the right framework for your application architecture, use decision matrices that evaluate Core SDK, DataFlow, Nexus, and Kaizen against your project's specific runtime, database, and node requirements.

PostgreSQL vs SQLite selection depends on your runtime and scaling needs; decision guidance pairs your chosen runtime with the appropriate datasource, evaluating criteria like concurrency, data volume, and deployment context.

The best way to select between Async and Local runtimes is applying evaluation criteria from decision matrices that map runtime characteristics to your framework choice, database pairing, and testing strategy.

To align testing strategy with your framework and runtime, follow recommended test-tier patterns that define clear workflows and node selection rules, ensuring your tests match the runtime and database decisions.

Yes, cross-framework interoperability is supported through defined reference patterns that guide how Core SDK, DataFlow, Nexus, and Kaizen interact, enabling multi-framework architectures with fallback strategies.

Node selection limitations arise when specific nodes lack compatibility with your chosen runtime or database; reference patterns and fallback strategies help anticipate these constraints and guide alternative node configurations.