White Papers

White Paper: Platform Engineering Challenges and Solutions

Issue link: https://read.uberflip.com/i/1387898

Contents of this Issue

Navigation

Page 0 of 5

Platform Engineering: Challenges and Solutions © 2020 Mirantis Inc. All Rights Reserved. Information is subject to change. | www.mirantis.com Hybrid- and multi-cloud can break the common-sense ergonomics and economics driving the rise of platform engineering. Here are some patterns useful for meeting these new challenges. Much has been written, over the past two years, about "platform engineering" — a job concerned with designing, building, maintaining, and extending a self-service, automation, and abstraction f ramework that makes platform components (e.g., Kubernetes, databases, services provided by underlying cloud f rameworks, etc.) consumable, performant, and manageable by service developers, application developers, and SREs. The illustration, below, shows where platform engineering fits in the job- description "stack." Is the platform engineering job really required, and is it distinct f rom other jobs (e.g., "DevOps," "SRE")? Absolutely. The rise of container orchestration on robust (but for newcomers, complicated) platforms like Kubernetes, and increasing use of Kubernetes as both the universal platform for (many) applications and the universal, pave-the-world f ramework for underlying inf rastructure and services creates massive opportunity (Plus tools! Standards! Best practices!) for: • Clean separation of concerns — Platform engineers can create an upward-facing API that lets service engineers consume and use NoSQL databases (e.g., Cassandra) or high-cardinality time-series databases and visualization f rameworks (e.g., Amazon

Articles in this issue

Links on this page

view archives of White Papers - White Paper: Platform Engineering Challenges and Solutions