Criteria for Cloud Recipes: Best Practices or Cost-Effective Solutions?

[SoTrx]

This is more of a discussion than a feature request.

What exactly are the criteria for Cloud recipes (especially Azure) to be included in this repository?

For local development recipes, we could say that a "good" local dev recipe is the smallest/simplest subset of resources needed to make the feature work.

However, for a Cloud recipe, this is less clear.
Should we consider these recipes as "recommended by the provider for production workloads"?
For instance, in Azure, should we default to leveraging Azure Verified Modules (AVM)?
These are implementations of Microsoft's Well-Architected Framework (WAF) and are the recommended approach by Microsoft. However, they may be overkill and cost-ineffective for certain scenarios.

Another way to define a "good" recipe could be as a "cost-effective" recipe, which introduces another dimension entirely.

I’d like to contribute to Cloud recipes — what criteria should I consider?

AB#13235

[Reshrahim]

Yes for Azure, it makes sense to use Azure Verified Modules in Recipes as these are standardized IaC modules. We did test creating a Recipe with AVM in a previous release of Radius but faced some issues due to old Bicep fork. Now that Radius is on official Bicep, you should be able to create Recipes with AVM for the existing supported resource types.

Feel free to drop in a PR if interested. We can work together on setting up guidance for Azure Recipes.