This article's tone or style may not reflect the encyclopedic tone used on Wikipedia. (May 2024) |
Platform engineering is a software engineering discipline focused on the development of self-service toolchains, services, and processes to create an internal developer platform (IDP).[1] The shared IDP can be utilized by software development teams, enabling them to innovate.[2][3]
Platform engineering uses components like configuration management, infrastructure orchestration, and role-based access control to improve reliability. The discipline is associated with DevOps and platform as a service practices.[2][3]
Purpose & Impact
editPlatform engineering aims to improve software engineering productivity by creating streamlined toolchains that can be used by developers. It can be used for digital transformation, or to expand CI/CD setups.[4]
According to a panel of experts at PlatformCon 2024, it was stated that building an internal developer platform can improve more than just developer productivity. Platform engineering, which centralizes best practices and components for development teams, is gaining prominence as DevSecOps practices and frameworks become increasingly embedded across organizations. Platform engineering aims to normalize and standardize developer workflows by providing developers with optimized “golden paths” for most of their workloads and flexibility to define exceptions for the rest. Organizations can follow one of two paths when developing a new platform engineering initiative. One option is to build an authentication and visualization layer that sits across multiple point tools — but this does not solve the underlying problems of legacy technology stacks and tooling silos. Therefore, this would likely not be a long-term solution. Alternatively, the organization could implement an internal developer platform (IDP)[5] that reduces the cognitive load on developers by bringing multiple technologies and tools into a single self-service experience.[6][7]
Platform engineering’s benefits include faster time to market, reduced security and compliance risk, and improved developer experience. Establishing a product-oriented culture and setting clear business goals are critical for success in platform engineering. Therefore it can be stated that platform engineering has increased importance wherever businesses strive to do more with less.
Criticism of Platform Engineering
editDespite its benefits, platform engineering faces several criticisms. One major concern is the complexity and overhead associated with building and maintaining such platforms. Additionally, creating a one-size-fits-all platform might not address the unique needs of all development teams, leading to inefficiencies and frustration. Siloed teams and a lack of focus on resolving operational issues can also hinder the effectiveness of the platforms created.
References
edit- ^ "What is an internal developer platform?". Red Hat. November 20, 2024. Retrieved December 7, 2024.
- ^ a b Perry, Morgan (November 22, 2023). "Platform Engineering vs. DevOps: What is the Difference?". Qovery. Archived from the original on February 23, 2024. Retrieved June 1, 2024.
- ^ a b Evans, Darren; McGhee, Steve (May 30, 2024). "Common myths about platform engineering". Google Cloud Blog. Archived from the original on May 31, 2024. Retrieved June 1, 2024.
- ^ Ghosh, Bijit (December 21, 2022). "What is platform engineering and how it reduce cognitive load on developers". Medium. Archived from the original on December 24, 2022. Retrieved June 1, 2024.
- ^ Abeysinghe, A. (October 2023). "Internal Developer Platform: A Technical Definition". WSO2.
{{cite web}}: CS1 maint: date and year (link) - ^ Joslyn, Heather (July 13, 2024). "What's the Impact of Platform Engineering?". The New Stack. Retrieved July 16, 2024.
- ^ Wald, Brian (July 9, 2024). "Platform Engineering Is for Everyone". The New Stack. Retrieved July 16, 2024.