18 lines
No EOL
1.8 KiB
XML
18 lines
No EOL
1.8 KiB
XML
<?xml version="1.0" encoding="utf-8" standalone="yes"?>
|
||
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
||
<channel>
|
||
<title>Platform Engineering :: IPCEI-CIS Developer Framework Documentation</title>
|
||
<link>http://localhost:1313/platform-engineering/index.html</link>
|
||
<description>Rationale IPCEI-CIS Developer Framework is part of a cloud native technology stack. To design the capabilities and architecture of the Developer Framework we need to define the surounding context and internal building blocks, both aligned with cutting edge cloud native methodologies and research results.
In CNCF the discipline of building stacks to enhance the developer experience is called ‘Platform Engineering’
CNCF Platforms White Paper CNVF first asks why we need platform engineering:</description>
|
||
<generator>Hugo</generator>
|
||
<language>en-us</language>
|
||
<atom:link href="http://localhost:1313/platform-engineering/index.xml" rel="self" type="application/rss+xml" />
|
||
<item>
|
||
<title>Reference Architecture</title>
|
||
<link>http://localhost:1313/platform-engineering/reference-architecture/index.html</link>
|
||
<pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
|
||
<guid>http://localhost:1313/platform-engineering/reference-architecture/index.html</guid>
|
||
<description>The Structure of a Successful Internal Developer Platform In a platform reference architecture there are five main planes that make up an IDP:
Developer Control Plane – this is the primary configuration layer and interaction point for the platform users. Components include Workload specifications such as Score and a portal for developers to interact with. Integration and Delivery Plane – this plane is about building and storing the image, creating app and infra configs, and deploying the final state.</description>
|
||
</item>
|
||
</channel>
|
||
</rss> |