AJR/TechRadarAJR
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update self-service-infrastructure.md

Browse Source
This commit is contained in:
Roland Edwards, AOE GmbH
2018-05-16 15:46:30 +02:00
committed by Daniel Pötzinger
parent 52625f6c78
commit 28b79b2795
1 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
radar/2017-10-01/self-service-infrastructure.md
View File

@@ -1,12 +1,12 @@
---
title: "Self service infrastructure"
title: "Self-service infrastructure"
ring: assess
quadrant: methods-and-patterns
---
With growing teams, growing projects and growing infrastructure we decided to follow the "You build it, you run it"-approach, and when we started to run Kubernetes, where we have a great abstraction layer between infrastructure and applications, we decided to make the developer teams write their own Helm charts.
By agreeing on just a couple of patters, this allows us to easily manage a microservice architecture with more than 60 Applications, without too much hassle managing infrastructure/runtimes for (amongst others) JVM, Go and PHP applications.
Most of the hosting/provisioning decisions are better kept at the team, as they are the ones who know how their application works. By providing a clear interface this became the cornerstone for running our microservice architecture, and keeping the amount of actual servers much lower than in projects with a centralized operations/IT team.
With growing teams, growing projects and growing infrastructures, we decided to follow the "You build it, you run it" approach, and when we started to run Kubernetes, where we have a great abstraction layer between infrastructure and applications, we decided to make the developer teams write their own Helm charts.
By agreeing on just a couple of patters, this allows us to easily manage a microservice architecture with more than 60 Applications, without too much hassle managing infrastructure/runtimes for (among others) JVM, Go and PHP applications.
Most of the hosting/provisioning decisions are better kept within the team, as the teams know how their applications work. By providing a clear interface, this became the cornerstone for running our microservice architecture, and keeping the amount of actual servers much lower than in projects with a centralized operations/IT team.
Eventually self service infrastructure, and "You build it, you run it", allowed us to give both our application developers as well as our infrastructure engineers more flexibility than one team explaining another team what to do, resulting in a better collaboration than before.
Eventually, self-service infrastructure, and "You build it, you run it", allowed us to give both our application developers as well as our infrastructure engineers more flexibility than one team explaining to another team what to do, resulting in a better collaboration than before.