Fact: Each Platform Is Unique
It can be tempting to think that if a solution works in one scenario, it will work in another; however, every platform serves a specific purpose, and what works for one might not fit another. Solutions should be tailored based on individual needs rather than a one-size-fits-all approach.
Fallacy: Platform Engineers Work Alone
The practice requires a collective effort and thorough team and responsibility mapping to ensure that everyone works together toward the same goal. Communication must flow seamlessly among service teams, designers, security experts and other stakeholders.
Fallacy: Security Is the Sole Responsibility of the Security Team
Every line of code and every architectural decision represents an entry point for attack and must be viewed through a security lens. Security testing must begin from the very start of any project and continue throughout development to the product’s release.
Fallacy: Platform Engineering Is Cost-Prohibitive
Platform engineering can reduce costs and simplify the complexity of various tools, workflows and dependencies, particularly when developers work from an internal platform that enables scalability and hastens time to launch by incorporating reusable components such as libraries, templates and other predefined resources while also enforcing standards and governance.
LEARN MORE: Maximize your platform engineering initiatives.
Fallacy: Adding Platform Engineering Always Slows Progress
A problematic adoption of platform engineering tends to increase friction unless there is buy-in from all participants and stakeholders. But platform engineering can also produce visible progress quickly, and many are surprised with successful implementations that have buy-in.
Fallacy: It Does Not Alter the Software Bill of Materials
The engineering nervous system employed through platform engineering becomes the bottom layer of almost every stack. It’s an evolving definition of stack components, vetted tools and software engineering ingredients.
It’s no surprise that platform engineering sometimes becomes a rock thrown into the gears of progress. Performed correctly, it becomes part of a successful DevOps operation through thoughtful integration. But to achieve that, platform engineers must be involved in projects as equal members. Without that collaboration, platform engineering grinds slowly toward teamwork, with an interregnum of small fires and hair removal by the fistful.
DIG DEEPER: Infrastructure as code is the backbone of platform engineering.
Fact: Platform Engineering Is Evolution, Not Revolution
Platform engineering techniques provide essential instrumentation for all elements of the platform, including DevOps, testing and hosted production instances, all with prescribed and consistent infrastructure. The consistency of platform engineering for the platform’s many manifestations means that there is cohesive binding between DevOps and the platform, wherever that platform exists, and on whichever turf it resides or moves toward.
Fallacy: Static Platforms Don’t Need Platform Engineers
This is wrong, both on-premises and in the cloud. Platform engineering isn’t a retirement plan. Instead, platform engineers are charged with keeping platforms greased for developers, software pipelines, compliance officers, security auditors, and security event and information management tools.
The resistance to platform engineering as the newest team member in software engineering often involves fear of the unknown. Many of the techniques used by platform engineers contribute to DevOps in the same way that DevOps weaves together interdisciplinary efforts between development and operations teams. Platform engineering evolves those relationships more formally, but not at the price of productivity. Instead, platform engineering can help carry the load.
UP NEXT: Five questions to ask before you start on platform engineering.
