<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rodrigo on Medium]]></title>
        <description><![CDATA[Stories by Rodrigo on Medium]]></description>
        <link>https://medium.com/@RodrigoDL?source=rss-e47e662813------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*jvSfgbbPXpWcA4TOM-A1Fg.jpeg</url>
            <title>Stories by Rodrigo on Medium</title>
            <link>https://medium.com/@RodrigoDL?source=rss-e47e662813------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 11:25:18 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@RodrigoDL/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[DevOps vs. Platform Engineering]]></title>
            <link>https://medium.com/blue-harvest-tech-blog/devops-vs-platform-engineering-7b2ff2df30de?source=rss-e47e662813------2</link>
            <guid isPermaLink="false">https://medium.com/p/7b2ff2df30de</guid>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[platform-engineering]]></category>
            <category><![CDATA[developer-experience]]></category>
            <dc:creator><![CDATA[Rodrigo]]></dc:creator>
            <pubDate>Wed, 05 Mar 2025 09:13:38 GMT</pubDate>
            <atom:updated>2025-07-11T12:18:13.254Z</atom:updated>
            <content:encoded><![CDATA[<h3>DevOps vs. Platform Engineering: Differences and Synergies Part 1</h3><p>· <a href="#207c">TLDR</a><br>· <a href="#3011">Part 1: History and Definitions</a><br>· <a href="#2c07">The history of Platform Engineering</a><br>· <a href="#d116">Team Topologies and Platform Engineering</a><br>· <a href="#77a7">SDLC Complexity from the DevOps perspective</a><br>· <a href="#6521">What is Platform Engineering</a><br>· <a href="#b3eb">Transversal Platform Teams vs Platform Engineering Teams</a><br>· <a href="#ee3d">What Platform Engineering is not</a><br>· <a href="#af8e">Conclusion</a><br> ∘ <a href="#4f58">Part 2: Contrasting approaches</a><br> ∘ <a href="#b5ec">Part 3: New concepts</a></p><blockquote>Disclaimer</blockquote><blockquote>This is an opinion piece on the discipline and set of practices that compose “Platform Engineering”, it is <strong>not</strong> about the <strong>job role </strong>of a “Platform Engineer”.</blockquote><h3>TLDR</h3><ul><li>Platform Engineering is a response to the complexities of DevOps by providing <strong>developer self-service</strong> experiences. It addresses the challenge of “You build it, you run it” when the complexity to do so exceeds an individual’s or team’s cognitive capacity <a href="https://medium.com/p/7b2ff2df30de/edit#6521">[1]</a>.</li><li>It aims to lower cognitive load by sharing solutions to common problems, synergising different skill sets from multiple teams and structuring automation via <strong>Internal Developer Portals</strong> (IDPs) and <strong>Golden Paths</strong>.</li><li>Platform Engineering establishes a platform layer between different DevOps Oriented teams, acting as a standardisation force and using self-service to prevent shadow operations. It also fƒosters communities for sharing the administration and development of common solutions</li><li>It is a step forward from DevOps, not <strong>backwards</strong> as an Ops team for the cloud, it leverages a lot of DevOps <strong>processes</strong> to achieve its objectives.</li></ul><h3>Part 1: History and Definitions</h3><h3>The history of Platform Engineering</h3><p>From: <a href="https://platformengineering.org/blog/the-story-of-platform-engineering">https://platformengineering.org/blog/the-story-of-platform-engineering</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vutifsaC2zechRZyLMNgPw.png" /></figure><p>Platform engineering arose from frustrations with DevOps adoption in many organisations.</p><p>While DevOps helped some teams, the increasing complexity of cloud-native technologies created problems for most, leading to developer burnout and overwhelmed operations teams.</p><p>So, the logical next step was to create “Internal Developers Platforms”.</p><p><strong>2010 Early Platforms:</strong> Tech giants like Google and Netflix began building platforms to improve efficiency, but smaller organisations lacked the resources and expertise to follow suit<strong>.</strong></p><p><strong>2018 Defining the Concept:</strong> In 2018, Evan Bottcher defined a digital platform as a self-service system of tools, services, and support, which should be treated as a product.</p><p><strong>2019 Team Topologies</strong>, the book Team Topologies introduced the concept of platform teams and their relationship with the rest of the organisation, highlighting the need for a clear separation of concerns.</p><p>The definition of “platform” they introduced is aligned with Evan Bottcher’s definition of a digital platform:</p><blockquote><em>A digital platform is a foundation of self-service APIs, tools, services, knowledge and support which are arranged as a compelling internal product. Autonomous delivery teams can make use of the platform to deliver product features at a higher pace, with reduced coordination</em></blockquote><p>*From the book <a href="https://teamtopologies.com/">https://teamtopologies.com/</a></p><h3>Team Topologies and Platform Engineering</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RgmdXhi6R44V912kzMw1Og.png" /></figure><p>*From the book <a href="https://teamtopologies.com/">https://teamtopologies.com/</a></p><p>On this image we see that if an organisation has small, distributed teams it is more likely to produce is a modular architecture but what it doesn’t show is that if these teams become silos, then the output will be a fragmented system.</p><p>This fragmented system will not have tools to <strong>standardise</strong> any operations and waste a lot of developer’s time solving the same problems as many times as teams it has. To say it in a different way the current distributed team model does not scale past a small number of teams, and this is where Platform Engineering shines.</p><p>We can use this discipline to <strong>scale</strong> the DevOps operations inside the distributed teams by following its practices like <a href="https://www.cortex.io/post/what-is-an-internal-developer-portal">Internal Developer Portals</a>, Golden Paths and forming Developer Communities around them. The way we can put into practice this idea is by forming a <strong>Platform</strong> <strong>Team</strong> that has a “Platform as Product” mindset, as it was first introduced in the book “<a href="https://teamtopologies.com/">Team Topologies”</a></p><p>We know that applications must have a place to run as compute resources and if <a href="https://en.wikipedia.org/wiki/Conway%27s_law">Conway’s Law</a> says that the organisation should mirror the software/system they want to produce, it follows that the platform where they run said software should also mirror it. To achieve this a different type of team is created that helps the <strong>stream</strong> <strong>aligned</strong> team lower the burden of creating and maintaining their own platform tailored to their specific product.</p><p>As described by the <a href="https://teamtopologies.com/">Team Topologies book</a>:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/566/1*BoRMg56fJ_KjN5JaahgX5w.png" /></figure><ul><li>The stream-aligned team maintains full ownership of building, running, and fixing their application in production.</li><li>The purpose of a platform team is to enable <strong>stream-aligned </strong>teams to deliver work with substantial <strong>autonomy</strong>.</li><li>The platform team provides internal services to reduce the cognitive load that would be required from stream-aligned teams to develop these underlying services.</li></ul><h3>SDLC Complexity from the DevOps perspective</h3><p>From <a href="https://www.youtube.com/watch?v=m1FBrO3ekkU">Platform Engineering vs DevOps</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*q4WiZr0SRGr_WIwcj48ntg.png" /></figure><p>*DevSecBizOps: Align developers and security efforts with business priorities to optimise value delivery. 🤣</p><p>All teams working with a DevOps mindset will have to solve this complexity one way or another. Either creating their own solution to their specific problems or by reusing a solution at the organisational level.</p><h3>What is Platform Engineering</h3><p>We now understand the reason for the emergence of Platform Engineering as a discipline and a have a description of what a Platform Engineering <strong>team</strong> should do to help the organisation, so we can start to describe what <strong>Platform Engineering</strong> is.</p><p>The industry broadly agrees that Platform Engineering addresses the growing complexity of DevOps at scale by empowering developers through self-service tools and collaborative communities. In essence, it’s “DevOps for the People”.</p><p>While DevOps focuses on enabling continuous software delivery, Platform Engineering supports teams in achieving this goal by simplifying processes and reducing mental strain through shared tools and teamwork.</p><ul><li>It utilises a lot of DevOps processes to deliver their own products (Internal Developer Portals, Golden Paths and other automation concepts)</li><li>It uses Continuous Integration and Delivery pipelines, Agile and Scrum project management.</li><li>It tries to solve the “You build it, you run it” at <strong>scale</strong> problem, that is when the complexity of the end-to-end system is bigger than one person or team’s cognitive ability.</li><li>It tries to lower this cognitive load by creating <strong>communities</strong> around shared goals to create shared solutions.</li><li>This also helps synergise the <strong>skillsets</strong> of individual contributors from different teams, that is where one team could have a lot of knowledge and experience on one topic and could complement another team that lacks it.</li></ul><p>To be able to do this it uses concepts such as <strong>Developers Communities</strong>, <strong>Internal Developers Portals </strong>and <strong>Golden Paths. </strong>This makes the Platform Team an standardisation force at the organisational level. By leveraging self-service and communities it avoids the usual outcome of “shadow operations” created by siloed developer teams, that try to solve a common problem implementing their own solution.</p><p>The end goal is to help teams scale their approach to software development by reducing the need to solve problems individually and instead in a concerted and autonomous fashion.</p><h3>Transversal Platform Teams vs Platform Engineering Teams</h3><p>The complexity of where to run software in production was historically provided by “<strong>transversal platform teams</strong>”. They are specialised in building and maintaining platform capabilities used by multiple product teams across a large organisation. However they risk becoming disconnected from their key stakeholders — developers — if they do not actively use the tools they build.</p><p>This disconnect often arises because the “transversal platform team” often doesn&#39;t have the need to use their own solutions, leading to misaligned priorities or ineffective tools. Not being users of their own tools starts showing when the mindset of building and maintaining platforms capabilities becomes a “Us vs Them” interaction.</p><p>This creates a gap between the needs of the day-to-day user and the needs of the creators of the system, devolving into the Dev vs Ops of the old days. Platform Engineering tries to solve this problem by shifting the focus from builders and maintainers to <strong>facilitators</strong> and specialised <strong>guideline</strong> providers.</p><h3>What Platform Engineering is not</h3><p>A lot of people are quick to view Platform Engineering as the replacement of the DevOps discipline because it has a lot of the same goals, i.e. help the developers deliver value in the form of deployments to production.</p><p>This was never the original intention of the pioneers of the discipline and instead it was meant to be a step forward at <strong>scale</strong>, not backwards into an “<strong>OPs </strong>team for the cloud”.</p><p>It is not meant to be an Ops team that acts as a gatekeeper or enforces policies on developers when they want to deploy their work to production, as traditional Ops teams used to do. This is what a ‘Transversal Platform Team’ often degrades into over time.”</p><p>It is more than an “X-as-a-Service” producer, that could be the outcome, but the Platform Engineering team is never fully responsible for the design, implementation and maintenance of these services. Rather works as a facilitator of these processes and the Developers <strong>Communities</strong> are ultimately responsible for the outcomes.</p><p>It is also not a general approach to software production as <strong>Continuous Delivery </strong>is, instead it facilitates the design of tools that use the CD approach to deliver and create software.</p><h3>Conclusion</h3><p>Platform Engineering and DevOps are complementary disciplines that address the same challenges at different scales. In small companies, the same team typically handles both. However, in larger organisations, a dedicated Platform Engineering team is necessary.</p><p>This team should act as facilitators rather than enforcers, bridging the gap between more oriented operational teams and software development teams. Their primary role is to foster strong internal communities, with building tools and services as a secondary focus.</p><p>Next articles to be published:</p><h4><strong>Part 2: Contrasting approaches</strong></h4><ul><li>What are the objectives of Platform Engineering</li><li>Comparison of what each discipline tries to solve</li><li>Traditional Ops team</li><li>DevOps oriented teams</li><li>Platform Engineering oriented Teams</li></ul><h4>Part 3: New concepts</h4><ul><li>Shared responsibility of services</li><li>Internal Developers Portals</li><li>DevOps</li><li>Platform Engineering</li><li>Golden Paths</li><li>DevOps</li><li>Platform Engineering</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7b2ff2df30de" width="1" height="1" alt=""><hr><p><a href="https://medium.com/blue-harvest-tech-blog/devops-vs-platform-engineering-7b2ff2df30de">DevOps vs. Platform Engineering</a> was originally published in <a href="https://medium.com/blue-harvest-tech-blog">Blue Harvest Tech Blog</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A lean Continuous Deployment, Testing and Integration Pipeline using CoreOS/Docker/Jenkins]]></title>
            <link>https://medium.com/@RodrigoDL/a-lean-continuous-deployment-testing-and-integration-pipeline-using-coreos-docker-jenkins-633d785232a7?source=rss-e47e662813------2</link>
            <guid isPermaLink="false">https://medium.com/p/633d785232a7</guid>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[coreos]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[docker]]></category>
            <category><![CDATA[docker-compose]]></category>
            <dc:creator><![CDATA[Rodrigo]]></dc:creator>
            <pubDate>Sat, 16 Dec 2017 16:56:13 GMT</pubDate>
            <atom:updated>2017-12-16T16:56:13.314Z</atom:updated>
            <content:encoded><![CDATA[<p>I wrote an article about how I created a small, lean, single server, CD/CI and Testing pipeline using CoreOS, Jenkins, and Docker. Feedback is welcome!</p><p><a href="https://github.com/bruj0/jenkins_pipeline">bruj0/jenkins_pipeline</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=633d785232a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>