select-cloudflare-components

To determine the right Cloudflare service for new features, you evaluate feature requirements against infrastructure capabilities. This assigns optimal services like D1, KV, R2, Durable Objects, Queues, or Workflows based on topology compliance and dependency chain analysis.

You need Cloudflare Workflows instead of standard Workers when your multi-step process requires orchestrated workflow management. Evaluating dependency chains ensures the topology aligns with Workers-first policies before assigning Workflows for complex, multi-stage edge-based applications.

The Workers-first topology policy is a standardized infrastructure strategy enforcing that service selection aligns with Cloudflare best practices. It eliminates architectural ambiguity by validating decisions against settled policies, ensuring production-ready system architecture design.

Yes, Cloudflare supports SQLite-backed Durable Objects for stateful connections. When a feature necessitates stateful connections, the architecture evaluation validates this assignment against infrastructure capabilities to ensure the resulting topology is production-ready.

Selecting an LLM provider for edge-based applications requires validating architectural decisions against specific LLM provider selection criteria (S-002). This ensures the chosen provider aligns with the Workers-first topology and overall infrastructure strategy.

Yes, you can use this approach to configure service bindings for Cloudflare Workflows. The evaluation applies to service binding configuration and dependency chain analysis, ensuring optimal service assignments and topology compliance across the infrastructure.