12 Scenarios of Failure: Applying Chaos Engineering to SAP | Guilherme Sesterheim
Plus, why you need to stop hiring only sr. engineers, the trifecta for cross-functional success & the importance of personal brand.
On this week’s episode, host
sit down with Guilherme Sesterheim, SAP DevOps SRE Engineer at AWS. Guilherme delves into applying Chaos Engineering and DevOps principles to SAP, a domain traditionally seen as risk-averse and resistant to rapid innovation.With expertise in both open-source technologies and SAP, Guilherme shares how he’s bringing modern practices to SAP environments at AWS. He explores how Chaos Engineering can be used to test and improve the resilience of SAP systems, focusing on HANA, SAP’s in-memory database. The discussion also touches on the challenges of integrating these practices within the SAP framework and the broader implications for SAP users and the tech industry.
“You can inject failures on the network, so let's add some latency. Latency in the SAP world is one of the hardest things to spot. Let's inject a system crash, let's inject some DNS failure, some resolution failure, and let's see what happens.”
Episode Highlights:
01:20 What does it mean to apply chaos engineering to testing SAP installation?
05:05 What does it mean to have DevOps around SAP?
06:58 Guilherme’s approach to DevOps practices around SAP
11:01 The challenge of handling installation and migration
12:50 How to start applying Chaos Engineering to your SAP instance
17:57 The 12 scenarios when you inject failures on SAP
18:24 How Guilherme ended up at AWS working on SAP
24:14 What’s next in DevOps Guilherme is excited about
Episode Transcript
The Download
The Download is engineering leadership content we’re reading, watching, and attending that we think you might find valuable.
1. The Leadership Trifecta for Cross-Functional Success
The trifecta of engineering, product and UX is common on front-line teams, but why does that stop as you go up the org chart?
Friend of the show and the
ICYMI: James also published a fantastic article with us last week “The Snow Melts At The Periphery” about how senior leaders can stay connected to the outside world.
2. Why you need to stop hiring only senior engineers
“Ambition, character and brains have little to do with experience.” –
,Whether you’re a startup that needs productivity from day one, or an enterprise with complex infrastructure, Anton’s recent article argues that these excuses shouldn’t hold you back from hiring junior engineers. Hiring juniors offers more potential candidates, fresh energy, and an adaptiveness that could help your team more than you think.
Measuring Impact: The GenAI Code Report (Sponsor)
Want to learn how engineering leaders are implementing GenAI and measuring their success? LinearB surveyed over 150 CTOs, VPs of Engineering, and Engineering Managers to answer these questions and more in their new GenAI Code Report.
Inside you’ll find:
12+ metrics to track the impact of your GenAI Initiative
How to measure the adoption, benefits, and risks of GenAI Code
Key insights from our survey conducted on 150+ CTOs, VPEs and Engineering Managers
3. Average Manager vs. Great Manager
This cartoon series from Julie Zhuo showcases the traits that set apart an average manager from a great one, including how to provide the right context or lead effective 1 on 1’s.
4. How to Stand Out as an Engineering Leader: Building Your Personal Brand
With the state of the job market making upward career development harder to attain, your personal brand can be the key piece that helps you stand out from the rest.
shared this checklist for EM’s to refine their brand in :Create a list of your beliefs
Focus on your reputation
Make sure your online presence is done correctly and is consistent across different media
Thanks for the mention! And nice cartoons by Julie Zhuo, a decade has passed but they are still amazing :)
I was surprised by the quality and originality of the illustrations in "the making of a manager", there added a lot to the book!