CNCF Platforms White Paper - I

Well, continue. post I decided to talk about it. CNCF whitepaper on platforms. The document consists of 7 point

1. Why platforms? The document begins with a list of the advantages of platforms and what problems they solve: Reduce cognitive load on food teams Improve the reliability and sustainability of products deployed on top of platforms Accelerate product development and delivery by reusing platform tools Reduce risks: security, regulatory, and functional bugs

• help to use the services and capacities of public clouds efficiently

2. What is a platform It defines the platform as a collection of features that are defined and presented in accordance with the needs of platform users. What’s important here is that all of these features are integrated together and provide the ability to execute typical user scenarios on the platform. Critically, not all platform teams need to implement their own capabilities. (These can be provided by cloud providers or internal teams within the organization.). Since these platforms are aimed at internal developers, they are called internal developer platform. Next, the authors separately analyze the maturity levels of the platforms Platform maturity Product developers can get the capabilities of the on-demand platform and immediately use them to run their applications Product developers can gain space for services and immediately use them to run piplins and tasks for storing artifacts, configuring and collecting telemetry Administrators of third-party software can get their dependencies on demand, for example, databases, and then use them in their decisions. Product developers can get a full template environment along with run-time and development-time services for specific scenarios (Web, ML, ...) Product developers and managers can monitor the functionality, performance and bones of deployed services through standard tools and dashboards

3. Attributes of successful platforms In this article, the authors describe the properties of platforms that Platform as a product - the creation of platforms should be approached as a product User experience - you need to focus on the experience of developers (DexEx, I mean him. I recently read a white paper.) The platform could offer a reusable supply chain workflow for building, scanning, testing, deploying, and observing a web application on Kubernetes. Such a workflow could be offered with an initial project template and documentation, a bundle often described as a golden path" Self-service - the ability to use services independently Reduced cognitive load for users - the platform should reduce the load Optional and composable – products should be able to use the desired parts of the platforms, and the missing parts close themselves Secure by default – security must be built into the default platform

4. Attributes of successful platform teams Platform teams are responsible for the following areas:

• study of user requirements and creation of roadmap features Marketing, Evangelizing and Advocating for the Values Platforms Offer Manage and develop interfaces for use and explore capabilities and services, including portal, API, documentation, templates and CI tools The most important thing is that platform teams must study the needs of platform users and continue to inform and continually improve the capabilities and interfaces that platforms provide. To do this, you can use standard product tools, for example, described in the book by Martin Kagan "Inspired", which I am talking about. earlier.

Continuation in posts 2 and 3.

#Kubernetes #SRE #DistributedSystems #PlatformEngineering #SoftwareDevelopment #Software #ProductManagement