kidwellj
/
findcommonground.uk
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Merge pull request #4 from eliasweingaertner/master 

Layout fixes - hope this works
This commit is contained in:
Rainer Zehnle 2015-12-08 15:05:14 +01:00
parent a69fe17090 efdd4e4242
commit e85778aa16
1 changed files with 2 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
_posts/2015-12-8-microservices-devopscon.md
View File

@ -1,7 +1,7 @@
---
layout: post
title: DevOpsCon Munich: Is it really about the tools?
subtite: A opinionated comment by Elias Weingärtner
subtitle: A opinionated comment by Elias Weingärtner
description:
category: general
author: Elias Weingärtner
@ -36,8 +36,6 @@ First of all, I am not the first person to make this claim. In fact, at the conf
Many speakers at the conference quoted the famous quote by Melvin Conway from 1967 that is commonly referred to as Conway's Law.
> Organizations which design systems ... are constrained to produce designs which are copies of the communication structures of these organizations
> <hr>
> <small> Martin Conway, 1967
Similar to as mentioned by Rainer Zehnle, this led to my assumption that effectively doing Microservices and DevOps somehow doesn't work well in matrix-based organizations. Effectively, matrix-based organizations are often monoliths in which a lot of projects are tightly coupled, due to shared responsibilities of project teams and individuals.
@ -48,5 +46,4 @@ As already mentioned by Rainer in his blog post, I was really impressed how the
I took a lot from the conference - and I have constantly asked myself the question afterwards if we're ready yet for DevOps and MicroServices as a organization. Are we? Probably not yet, although we're certainly on the right track. And we're in good company: From many talks at the coffee table I got the feeling that many companies in the German IT industry are in the same phase of transition as we are. How do we get more agile? How do we do microservices? Should we have a central release engineering team? Or leave that to DevOps? I am excited which answers we will find at Haufe. We'll keep you updated. Promised.
[1] Per Brinch Hansen. 1970. The nucleus of a multiprogramming system. Commun. ACM 13, 4 (April 1970), 238-241. DOI=http://dx.doi.org/10.1145/362258.362278
[2] http://www.opengroup.org/austin/papers/posix_faq.html
[2] http://www.opengroup.org/austin/papers/posix_faq.html