Showing posts from 2018

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:

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.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 & secur…

micrxchg 2018: Serverless and Containers

The 2 days of "The Microservices Conference in Berlin - 2018" where packed with talks that clearly demonstrate that the world of micro services is based mainly on two topics: Serverless computing and containers. Users either go to the public cloud providers and use the existing frameworks there, e.g. Lambda, API Gateway, DynamoDB etc. on AWS, or users build their own platforms on top of Kubernetes (or a Kubernetes variant).

The videos are available on the microXchg YouTube channel, my own talks:

The slides for my own talks are available via SlideShare:

Root for all - measuring DevOps adoption - microxchg 2018 - Schlomo Schapiro, see also Root for All - A DevOps Measure? blog article

Kubernetes - Shifting the mindset from servers to containers - microxchg 2018 - Schlomo Schapiro, see also Using Kubernetes with Multiple Containers for Initialization and Maintenance blog article.

Cloud means DevOps - No Cloud without DevOps

I strongly believe that you can't be successful in the Cloud without also adopting DevOps. Here is why.

My latest definition of DevOps is
if every person uses the same tool for the same jobcodified knowledge:
everybody contributes his part to common automationif all people have the same privileges in their toolingif human error is equally possible for Dev and Opsreplacing people interfaces by automated decisions and processes but most of all DevOps is the result of doing the right thing and not a process, methodology or even tool set of its own.

Looking closely at public cloud vendors and their interfaces I see a close correlation with this DevOps definition. Cloud vendors give every person the same interfaces and tools to work withare API based and make it really simple to code the entire setupgive all users the same privileges - that of a customerlet all their users make the same mistakes indisccriminatelyprovide most change requests through automation and automated decisions For …