-
Couldn't load subscription status.
- Fork 50
Concept overview page #1564
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Concept overview page #1564
Conversation
There was a problem hiding this 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 |
There was a problem hiding this comment.
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.
| * 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 |
There was a problem hiding this comment.
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
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]>

Revised Concept section.