Artwork

Conteúdo fornecido por Grant Ingersoll. Todo o conteúdo do podcast, incluindo episódios, gráficos e descrições de podcast, é carregado e fornecido diretamente por Grant Ingersoll ou por seu parceiro de plataforma de podcast. Se você acredita que alguém está usando seu trabalho protegido por direitos autorais sem sua permissão, siga o processo descrito aqui https://pt.player.fm/legal.
Player FM - Aplicativo de podcast
Fique off-line com o app Player FM !

Mikolaj Pawlikowski – Chaos Engineer, Crash Testing Your Applications #97

44:27
 
Compartilhar
 

Manage episode 273726667 series 2565702
Conteúdo fornecido por Grant Ingersoll. Todo o conteúdo do podcast, incluindo episódios, gráficos e descrições de podcast, é carregado e fornecido diretamente por Grant Ingersoll ou por seu parceiro de plataforma de podcast. Se você acredita que alguém está usando seu trabalho protegido por direitos autorais sem sua permissão, siga o processo descrito aqui https://pt.player.fm/legal.

Welcome to another episode of Develomentor. Today's guest is Mikolaj Pawlikowski!
Mikolaj Pawlikowski has been a chaos engineer for about four years. He began with a large distributed Kubernetes-based microservices platform at Bloomberg. Mikolaj is the creator of the Kubernetes Chaos Engineering tool PowerfulSeal, and the networking visibility tool Goldgpinger. He is an active member of the Chaos Engineering community and speaks at numerous conferences.

If you are enjoying our content please leave us a rating and review or consider supporting us

Quotes

“I spent half of my time at the company that employed me and payed me roughly half of the money that I’d get if I was working there full time. During the other half of the time I had to cram in all the classes that you would normally have.”

“If you have your laptop and it runs for 10 years, you assume it is basically going to run forever. But if you have 1000 laptops, you’re going to start to seem them going down.”

“You can’t ever properly test things in any other environment than production. Because the data is going to be slightly different and the patterns of users will be slightly different.”

“We want to minimize the blast radius. The number of things that can be affected by what we do. In the practice of chaos engineering, it’s not completely crazy to introduce some of that failure to production systems.”

—Mikolaj Pawlikowski

Additional Resources

Sign up for Mikolaj’s newsletter for the latest on chaos engineering – https://chaosengineering.news/

Mikolaj’s Book – Chaos Engineering: Crash Test Your Applications – https://www.manning.com/books/chaos-engineering

Past Develomentor Episodes to check out:

Ep. 15 Kelsey Hightower – Tech Support to Dev Advocate to Keynote Speaker

Charity Majors – Systems Engineer & Cofounder of Honeycomb.io #66

You can find more resources in the show notes
To learn more about our podcast go to https://develomentor.com/
To listen to previous episodes go to https://develomentor.com/blog/

Connect with Mikolaj Pawlikowski
LinkedIn
Twitter
https://mikolajpawlikowski.com/
https://chaosengineering.news/

Follow Develomentor
Twitter: @develomentor

Support the show
  continue reading

140 episódios

Artwork
iconCompartilhar
 
Manage episode 273726667 series 2565702
Conteúdo fornecido por Grant Ingersoll. Todo o conteúdo do podcast, incluindo episódios, gráficos e descrições de podcast, é carregado e fornecido diretamente por Grant Ingersoll ou por seu parceiro de plataforma de podcast. Se você acredita que alguém está usando seu trabalho protegido por direitos autorais sem sua permissão, siga o processo descrito aqui https://pt.player.fm/legal.

Welcome to another episode of Develomentor. Today's guest is Mikolaj Pawlikowski!
Mikolaj Pawlikowski has been a chaos engineer for about four years. He began with a large distributed Kubernetes-based microservices platform at Bloomberg. Mikolaj is the creator of the Kubernetes Chaos Engineering tool PowerfulSeal, and the networking visibility tool Goldgpinger. He is an active member of the Chaos Engineering community and speaks at numerous conferences.

If you are enjoying our content please leave us a rating and review or consider supporting us

Quotes

“I spent half of my time at the company that employed me and payed me roughly half of the money that I’d get if I was working there full time. During the other half of the time I had to cram in all the classes that you would normally have.”

“If you have your laptop and it runs for 10 years, you assume it is basically going to run forever. But if you have 1000 laptops, you’re going to start to seem them going down.”

“You can’t ever properly test things in any other environment than production. Because the data is going to be slightly different and the patterns of users will be slightly different.”

“We want to minimize the blast radius. The number of things that can be affected by what we do. In the practice of chaos engineering, it’s not completely crazy to introduce some of that failure to production systems.”

—Mikolaj Pawlikowski

Additional Resources

Sign up for Mikolaj’s newsletter for the latest on chaos engineering – https://chaosengineering.news/

Mikolaj’s Book – Chaos Engineering: Crash Test Your Applications – https://www.manning.com/books/chaos-engineering

Past Develomentor Episodes to check out:

Ep. 15 Kelsey Hightower – Tech Support to Dev Advocate to Keynote Speaker

Charity Majors – Systems Engineer & Cofounder of Honeycomb.io #66

You can find more resources in the show notes
To learn more about our podcast go to https://develomentor.com/
To listen to previous episodes go to https://develomentor.com/blog/

Connect with Mikolaj Pawlikowski
LinkedIn
Twitter
https://mikolajpawlikowski.com/
https://chaosengineering.news/

Follow Develomentor
Twitter: @develomentor

Support the show
  continue reading

140 episódios

Todos os episódios

×
 
Loading …

Bem vindo ao Player FM!

O Player FM procura na web por podcasts de alta qualidade para você curtir agora mesmo. É o melhor app de podcast e funciona no Android, iPhone e web. Inscreva-se para sincronizar as assinaturas entre os dispositivos.

 

Guia rápido de referências