Add FAQ for Radius vs. KubeVela (#1001)

* add faq for radius vs. kubevela Signed-off-by: Will Tsai <[email protected]> * spelling override Signed-off-by: Will Tsai <[email protected]> --------- Signed-off-by: Will Tsai <[email protected]>
radius-project · Dec 13, 2023 · c33086c · c33086c
1 parent 65e664c
commit c33086c
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 1 deletion.
diff --git a/.github/config/en-custom.txt b/.github/config/en-custom.txt
@@ -1221,3 +1221,4 @@ Newstrail
 postgresql
 natively
 NuGet
+KubeVela
diff --git a/docs/content/concepts/faq/index.md b/docs/content/concepts/faq/index.md
@@ -188,4 +188,8 @@ Where .NET Aspire is focused on the .NET experience from moving from local devel
 
 ### How does Radius compare to Azure Developer CLI (azd)?
 
-The [Azure Developer CLI](https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/) is an open-source tool that provides developer-friendly commands to simplify the process of building, deploying, and managing Azure resources. While both azd and Radius are geared towards the development and deployment workflows, the most apparent difference is that azd can be only be used to manage Azure resources, whereas Radius supports multiple cloud providers. Radius also introduces a way to model (and not just deploy) entire applications and automate these through [Recipes]({{< ref "guides/recipes/overview">}}), which allows for complete [separation of concerns]({{< ref "collaboration-concept" >}}) between operators and developers. With azd, even though developers may leverage CLI templates to deploy infrastructure, they still need to understand the underlying infrastructure and how to connect to it.
+The [Azure Developer CLI](https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/) is an open-source tool that provides developer-friendly commands to simplify the process of building, deploying, and managing Azure resources. While both azd and Radius are geared towards the development and deployment workflows, the most apparent difference is that azd can be only be used to manage Azure resources, whereas Radius supports multiple cloud providers. Radius also introduces a way to model (and not just deploy) entire applications and automate these through [Recipes]({{< ref "guides/recipes/overview">}}), which allows for complete [separation of concerns]({{< ref "collaboration-concept" >}}) between operators and developers. With azd, even though developers may leverage CLI templates to deploy infrastructure, they still need to understand the underlying infrastructure and how to connect to it.
+
+### How does Radius compare to KubeVela?
+
+[KubeVela](https://kubevela.io/) is an open-source platform that provides a higher level of abstraction for application deployments. Similar to Radius, it allows developers to define applications and their components, deployment across cloud providers or on-prem, and automated infrastructure provisioning with pre-defined templates. However, unlike Radius, KubeVela does not allow for modeling of connections between resources to set environment variables, configure access credentials, and more that make it simpler for developers to deploy and access resources.