Skip to content

Conversation

@zachcasper
Copy link
Collaborator

Revised Concept section.

Copy link
Contributor

@Reshrahim Reshrahim left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Some comments on the first part

weight: 80
---

## Introduction
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a great start to introducing Radius. One area that struck me as I read through this was what problems Radius helps solve and what do I get using Radius in an IDP. Some of the things we could highlight is
enabling platform engineers to create org specific resource catalog with guardrails, portable application centric abstractions to deploy apps across cloud providers and platforms.

I liked Dapr's overview
image

Comment on lines +47 to +31
* Enforce separation of concerns between application developers and platform engineers
* Define resource types which are higher level and more application oriented
* Eliminate the need for developers to handle low-level infrastructure details
* Ensure portability between cloud providers and container platforms
* Enforce infrastructure security, operational, and cost best practices
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

some of this can be bubbled up top in the intro

rad-ci-bot and others added 5 commits October 27, 2025 17:08
Signed-off-by: Zach Casper <[email protected]>
Signed-off-by: Zach Casper <[email protected]>
Signed-off-by: Zach Casper <[email protected]>
Signed-off-by: Zach Casper <[email protected]>
Signed-off-by: Zach Casper <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants