Schlomo Schapiro

As I am writing this, my last minutes of employment at Deutsche Bahn ( DB Systel , DB) are running out. Tomorrow I will start my new job at Forto – time to look back at my 4 years with DB. This was my first time working at a really large company, even a corporation. 320,000 employees is really a lot and till the very last week I met new people with interesting topics. Working at such a large company – especially one with so many subsidiaries – was a novel experience for me. I learned a lot about corporate politics and about the motivating factors in such a large organization. For me these last 4 years were a very good time, where I was allowed to work in a very interesting position (Chief Architect Cloud in the CTO Team of DB Systel) and together with very interesting and inspiring colleagues. I learned something from every one of my colleagues, and I would like to take this moment to tell you all a big thank you for this time together. A lot happened during those years, and I ...

I talked about this at the GitOpsCon EU 2021 and at Berlin DevOps Meetup 2021-11: The GitOps Journey Video The GitOps Journey Slides I also talked about this in a more expanded version at Enterprise Code 2021 and Continuous Lifecycle 2021: The Role of GitOps in IT-Strategy Slides And if you understand German, please watch this full features recording of my talk: GitOps is most definitely one of the hype words of 2021. No self-respecting tool fails to market itself as a "GitOps tool, even if is only remotely related to the GitOps principles defined by the CNCF GitOps Working Group . But where does GitOps fit into an IT strategy? In my opinion GitOps should be the centerpiece of every modern IT strategy! The GitOps journey takes the hype surrounding GitOps to build a solid, automation-focused, long-term sustainable IT strategy. A strategy that uses standard "GitOps" tools together with o...

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.

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 job codified knowledge: everybody contributes his part to common automation if all people have the same privileges in their tooling if human error is equally possible for Dev and Ops replacing 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 with are API based and make it really simple to code the entire setup give all users the same privileges - that of a customer let all their users make the same mistakes indisccriminately provide most change requests through auto...