DevOps September 2018: Culture vs. Tools

"Culture eats strategy for breakfast" is a well known quote that applies especially well to DevOps (good example). The two DevOps events in Berlin couldn't be more different and prove this idea:

  1. The DevOpsDays Berlin 2018 (a 2 day conference) was focused entirely on culture and delivered a solid collection of inspirational talks and success stories. Tooling was limited to a few ignite talks and the afternoon workshops, that happened at the same time as the open space sessions.
  2. The DevOps Berlin Meetup 09.2018 (an evening event) was all about tools. 3 talks about specific tools gave new and specific ideas about how to improve: automated database schema management with Flyway, Open Source CI with Concourse CI, Clickhouse the best backend for Graphite metrics collection.
At both events I gave an ignite talk about Compliance DevOps that shows why it is important to extend our DevOps approach also to the automation of non-functional requirements like IT architecture & security governance. As a result, compliance can be attested by the CI/CD pipelines and is a natural part of the development cycle:
For me both events were valuable and both provided me with new ideas and insights. Especially the quarterly local meetup is a good place to network in Berlin, meet former colleagues and to get to know interesting companies in Berlin, like Solaris Bank who kindly hosted this meetup.

Further reading about my DevOps topics:

Location: Anna-Louisa-Karsch-Straße 2, 10178 Berlin, Deutschland

Comments

Post a Comment

Like this content? You could send me something from my Amazon Wishlist. Need commercial support? Contact me for Consulting Services.

Popular posts from this blog

WARNING is a waste of my time

Image
How many log levels do you know? How many log levels are actually useful? At Relax and Recover we had an interesting discussion about the use of the WARNING log level. I suddenly realized that in a world of automation, I need only two log levels: ERROR and everthing else. ERROR means that I as a human should take action. Everything else is irrelevant for me. So far for the user side. As a programmer the choice of log level is sometimes much more difficult. As a programmer I might not want to decide for the user if some problem is an ERROR or not. The obvious solution is to issue a WARNING in an attempt to shed the responsibility of making a decision. But in an automated world that does not help me as an admin to run the software better. WARNINGS for most cases only create extra manual work because somebody needs to go and check some log file and decide if there actually is a problem. I would rather have the software make that decision and I would be happy to fix or readjus
Read more

The Demise of KaiOS - Alcatel 3088X

Image
I was really excited, when Firefox OS became commercially available as KaiOS for "smart" feature phones. Unfortunately the high hopes I had put into this platform have been utterly shattered. I was recently looking for a button phone that had only three requirements : very good battery run time, at least several days or a week of standby without charging easy backup or even synchronization of the contacts VoLTE support to benefit from LTE coverage  In Theory... On paper, KaiOS phones look like the perfect match for those requirements. PhoneCopy for KaiOS is a cloud synchronization service that comes with an app for KaiOS (and many other platforms) to synchronize contacts and other phone content to the cloud (and back). With batteries of 1500 mAh and more , KaiOS phones have the potential to deliver outstanding battery performance. The Alcatel 3088X , for example, boasts "up to 300h standby and more than 7h talk time" with a 1530 mAh battery: Battery specification
Read more

Mission Impossible: Complete Disaster Recovery for Google Workspace

Image
I'm a frequent user of Google Workspace and even accept the switch from free to paid for my family domain . One topic has always been on my to-do list: Proper backups to support disaster recovery after a major problem. It turns out that Google Workspace has a significant flaw: It is technically impossible to create a full backup of all data and to restore that! Google simply doesn't offer any API for that. As a result, all backup vendors are forced to work with the regular APIs. As a result, not everything in Google Workspace can be stored in a backup, e.g. Google Sites (new, not classic). Some content, like Google Drawings and others, can only be backed up as a static file (e.g. PDF) and not restored into a new Google Drawing. Google itself doesn't offer much on backup and disaster recovery: Recover deleted files and folders for Drive users Restore deleted shared drives or their files How to mitigate ra
Read more