Platform Engineering is not replacing DevOps.pdf

This short article aims to explain the place Platform Engineering takes in (complex) modern software engineering systems and what problems it can solve.

1. Platform Engineering is not replacing
DevOps

2. Traditional


In the "traditional" software engineering approach the development team responsibility focus
is limited for both process and stack. Teams focus on development of new functionality and
the majority of the infrastructure/platform resources and their configuration is provisioned on
behalf of the application team with a strong dependency on teams who provide these
services.

3. DevOps
Using a DevOps approach, teams take end-to-end ownership, ideally covering the entire value
stream. Teams now no longer just develop new features but also have the responsibility for
operational activities, manage cloud spend, and provision the required infrastructure resources
and their configuration themselves, where the "landing zones" are provided by a platform team.

4. Platform Engineering


Platform Engineering is an evolution to DevOps in which, on team level, the operational model
remains the same. This means that the ownership and accountability do not change for an
application team. What is introduced are centrally provided reusable components and services.
These components and services are part of the platform delivered with a product-mindset,
offered on a self-service basis, effectively providing paved-paths for application teams to
leverage.

5. Read More: https://www.industry-techoutlook.com/cxo-viewpoint/platform-engineering-is-not-replacing-devops-nid-509.html