Adding version 1.1 to the platforms whitepaper#77
Adding version 1.1 to the platforms whitepaper#77cmcgalliard wants to merge 5 commits intoCloud-Native-Platform-Engineering:mainfrom
Conversation
✅ Deploy Preview for cnpe ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
platforms-whitepaper/latest/index.md
Outdated
| 1. Administrators of third-party software can provision required dependencies like databases on demand and easily install and run that software. | ||
| 1. Product developers can provision complete environments from templates combining run-time and development-time services required for specific scenarios, such as web development or MLOps. | ||
| 1. Product developers and managers can observe functionality, performance, and cost of deployed services through automatic instrumentation and standard dashboards. | ||
| **Level 1: Provisional \-** Capabilities are built out of necessity by temporary or voluntary staff, leading to erratic adoption, ad hoc operations, and measurement. |
There was a problem hiding this comment.
Formatting here looks a bit off when comparing to the other numbered lists. Perhaps adding a bullet point for each point could make it more in line with the rest of the indentation.
There was a problem hiding this comment.
updated to follow the pattern in the rest of the document.
abangser
left a comment
abangser
left a comment
There was a problem hiding this comment.
Loving this. I have added comments where I think our baseline may be creating chattier diff than necessary. I know it is annoying to do that update and merge it into this branch so not necessarily saying we have to do that, but wanted to call it out so we had the chance!
platforms-whitepaper/latest/index.md
Outdated
| A good platform provides a consistent, opinionated user experience for using and managing its capabilities and services, such as Web portals, project templates, and self-service APIs. | ||
|
|
||
| According to Atlassian [[1]], "platform teams create capabilities that can be used by numerous stream-aligned [product] teams with little overhead.... platform teams minimize resources and cognitive load of the stream-aligned [product] team... platform teams can create a cohesive experience that spans across different user experiences or products." | ||
| According to Atlassian [[1]], "platform teams create capabilities that can be used by numerous stream-aligned [product] teams with little overhead…. platform teams minimize resources and cognitive load of the stream-aligned [product] team… platform teams can create a cohesive experience that spans across different user experiences or products." |
There was a problem hiding this comment.
Did we mean for this formatting change?
There was a problem hiding this comment.
No, and it looks weird in the preview. This should go back to what it was.
platforms-whitepaper/latest/index.md
Outdated
| 1. **Optional and composable**. Platforms are intended to make product development more efficient, so they must not be an impediment. A platform should be composable and enable product teams to use only parts of its offerings. It should also enable product teams to provide and manage their own capabilities outside of the platform's offerings when necessary. For example, if a platform doesn't provide a graph database and it's required for a product, it should be possible for the product team to provision and operate a graph database themselves. | ||
| 1. **Secure by default**. A platform should be secure by default and offer capabilities | ||
| to ensure compliance and validation based on rules and standards defined by the organization. | ||
| 1. **Secure and compliant by default**. A platform should be secure by default and offer capabilities to ensure compliance and validation based on rules and standards defined by the organization. Security, governance, and compliance requirements for the business should be baked into the platform, reducing users' cognitive burden while ensuring consistent enforcement. |
There was a problem hiding this comment.
Need to split sentences to new lines here.
|
|
||
| While platforms promise lots of value, they also bring challenges like the | ||
| following which implementers should keep in mind. | ||
| While platforms promise lots of value, they also bring challenges like the following which implementers should keep in mind. |
There was a problem hiding this comment.
This is an example where the baseline version didn't have a sentence per line making the diff bigger in this. Not sure if it is worth changing, but wanted to call it out if we want a cleaner final diff.
There was a problem hiding this comment.
I agree here - should we fix first, then rebase? Or should we let this PR fix it for the "latest", and I can review the v1.0 file and adjust accordingly.
| compositions for application team use | ||
| 1. Ensure platform teams are staffed appropriately for their domain and number | ||
| of customers | ||
| 1. Seek to build the thinnest viable platform layer over implementations from managed providers |
There was a problem hiding this comment.
This list also should be updated in the baseline if we choose to go that way.
|
|
||
| Categories of metrics that will help enterprises and platform teams understand | ||
| the impact of their platforms include the following: | ||
| Categories of metrics that will help enterprises and platform teams understand the impact of their platforms include the following: |
There was a problem hiding this comment.
Another baseline update if we choose to improve that.
| The following graphic illustrates the relationships between products, platforms, and capability providers. | ||
|
|
||
| <img src="assets/platform_components.png" width=600px /> | ||
| <img src="../assets/platform_components.png" width=600px /> |
There was a problem hiding this comment.
Baseline update? or why else changed? 🤔
There was a problem hiding this comment.
It's not showing either way correctly - this is me trying to get it to work. I've realized there is no 'platform_components.png'
There was a problem hiding this comment.
I'm checking on this in the main branch
| </tr> | ||
| </table> | ||
|
|
||
| | Capability | Description | Example CNCF/CDF Projects | |
There was a problem hiding this comment.
If we choose to keep md, I think this should be updated in the baseline (and may be enough for me to advocate we make all the baseline updates) as this is one of the areas with the highest visibility of people wanting to make sure projects are correctly listed.
4 participants
No description provided.