Today’s agile cross-functional teams usually contain T-shaped (or even Pi-shaped) engineers that embrace the DevOps Culture. They can help the team increase its autonomy by owning every aspect of the team’s product (or domain), cradle to grave, including runtime management and support. Traditionally, owning the platform was a step too far; leave this bit to the experts (and go cloud-native).
However, increasing levels of automation in every area have changed this. Pipelines as code (e.g. Jenkinsfile), Immutable Infrastructure as code (e.g. Terraform), Containers as code (e.g. Dockerfile), Container Scheduling as code (e.g. Docker in Swarm Mode and Kubernetes), and Service Orchestration as code (e.g. Compose-files and Docker Stack) all conspire to empower DevOps focused cross-functional teams to run their product on their own cloud-provider-agnostic Microplatforms.