Pureperformance

Have you ever thought about reorganizing data allocation based on production telemetry data? Have you ever thought about shifting compiler budgets to parts of your code that is heavily executed based on profiling information captured from your real end users? Whether the answer is yes or no you will be fascinated by Taras Tsugrii, Software Engineer at Facebook, who is sharing his experience on optimizing everything from compilers, to databases, distributed systems or delivery pipelines.If you want more after listening to this episode check out his recent talk at Neotys PAC titled “Old pattern powering modern tech”, subscribe to his substack newsletter, his hashnode blog, or the conference recordings of Performance Summit and Scaling Continuous Delivery.https://www.linkedin.com/in/taras-tsugrii-8117a313/https://www.youtube.com/watch?v=itOCQvk_LAshttps://softwarebits.substack.com/https://softwarebits.hashnode.dev/https://www.youtube.com/channel/UCt50fEvgrEuN9fvya8ujVzAhttps://www.youtube.com/channel/UCWf9HxiBud

Googles Census, OpenCencus, OpenTelemetry and AWS Distro for OpenTelemetry. Our guest Jaana Dogan, Principal Engineer at AWS, has been working in observability over many years and definitely had a positive impact on the where OpenTelemetry is today. In this episode Jaana (@rakyll) explains which problems the industry, and especially cloud vendors, try to solve with their investment in open source standards such as OpenTelemetry. She gives an update where OpenTelemetry is, the next upcoming milestones such as metrics and logs and what a bright future with OpenTelemetry being widely adopted could bring.https://twitter.com/rakyllIf you are interested in learning more – here are the links we discussed during the podcast: https://github.com/open-telemetryhttps://github.com/open-telemetry/opentelemetry-specificationhttps://github.com/open-telemetry/opentelemetry-protohttps://github.com/open-telemetry/opentelemetry-collectorhttps://github.com/open-telemetry/communityhttps://o11yfest.org/

Performance Engineering is not about running a performance test twice a year. That is just a poor attempt trying to validate your non functional requirements.Roman Ferstl, Managing Directory at Triscon, has discovered his love for performance engineering while optimizing code for software used in a space program. He then founded Triscon who is now helping to establish and scale performance engineering at large enterprises. In this episode we get his insights on how he approaches a new project, which bottlenecks to address first and how to motivate more people within an organization to invest in performance engineering.If you want to learn more don’t miss to check out Roman’s presentation from Perform 2021 titled “Turbocharging your Performance Engineering teams to scale efficiently”https://www.linkedin.com/in/roman-ferstl/https://www.triscon-it.com/en/https://perform.dynatrace.com/2021-americas/breakouts-single-day-3-turbocharging-your-performance-engineering-teams

To k8s or not – that should be the first question to answer before considering k8s. Granted – in many cases k8s is going to be the right choice but don’t just default to k8s because its hip or cool.In this episode we have Christian Heckelmann (@wurstsalat), DevOps Engineer at ERT, talking about his journey with k8s which started with installing k8s 1.9 on bare metal. He gives a lot of great advice based on his presentation “How not to start with k8s” such as Understand Networking, Don’t use :latest, Set Resource Limits, Train The People, Provide Templates and more.To get started with Kubernetes we encourage you to look at the YouTube Tutorials posted on TechWorld with Nana.https://twitter.com/wurstsalathttps://docs.google.com/presentation/d/1EL9OYe-1eOPXh6U8SMHnQxs8pcmr01d-uwoWoFnzUaY/edit#slide=id.g5420f4ebeb_0_5https://www.youtube.com/channel/UCdngmbVKX1Tgre699-XLlUA

You heard about Continuous Integration, Continuous Delivery and Continuous Deployment. Liquid Software aims to provide the next step towards Trusted Continuous Updates in the DevOps World.In this episode Baruch Sadogursky, DevOps Advocate from JFrog, explains how as engineers we need to add “Updateability” to our non-functional requirements and how product managers and marketing have to forget about traditional releases but think about incremental delivery of value. Baruch (@jbaruch) also promised to send everyone a hard copy of his book “Liquid Software” if you send him a direct message – so – make sure you do that and also check out the details on our discussion of uniquely identifying artifacts through Build-Info.https://www.linkedin.com/in/jbaruch/https://twitter.com/jbaruchhttps://drive.google.com/file/d/1PUb67FxM-eTtdyLNGPc-fGTcCJii-keE/viewhttps://github.com/jfrog/build-info

Software security is about securing websites against malicious attacks or using firewalls to prevent hackers entering your enterprise network. While this is part of software security there is much more that needs to be done – especially as more organizations are developing critical software it is important to protect the whole software delivery lifecycle from any malicious attacks along the supply chain.In this episode we have Michael Plank, Technical Product Manager at Dynatrace, talk about his latest blog post titled How Dynatrace protects its software development and delivery life cycle against supply chain attacks. We learn about attack vectors from development workstation until production deployment. He covers the strategies ranging from static to dynamic code analysis, vulnerability detection or code signatures. Tune in and learn that building secure software is more than ensuring your users have hard to crack passwords!https://www.dynatrace.com/news/blog/how-dynatrace-protects-its-software-development-

If you are not a gamer you may have never heard about Cyberpunk 2077. If you are – you may know about the challenges during their latest release.Dave Farley (@davefarley77), Co-Author of best seller Continuous Delivery, has been an engineering large and complex systems for decades. His work helped elevate our industry around Continuous Delivery and DevOps. In this episode he shares his learnings from failed projects like Cyberpunk as well as his own latest experiences around that picking the latest technology might be fashionable but is not always the smartest choice.To learn more about Dave check out Continuous Delivery website that also links to his YouTube Channel hosting some of the episodes he was referencing in the podcast.https://twitter.com/davefarley77https://www.amazon.com/Continuous-Delivery-Deployment-Automation-Addison-Wesley/dp/0321601912#ace-g9859629705https://www.continuous-delivery.co.uk/https://www.youtube.com/channel/UCCfqyGl3nq_V0bo64CjZh8g

Nobody has foreseen the global pandemic that put a lot of chaos in all our lives recently. Let’s just hope we learn from 2020 to better prepare on what might be next.The same preparation and learning also goes for Chaos in our distributed systems that power our digital lives. And to learn from those stories and better prepare for common resiliency issues we brought back Ana Medina (@ana_m_medina), Chaos Engineer at Gremlin. As a follow up to our previous podcast with Ana, she is now sharing several stories from her chaos engineering engagements across different industries such as finance, eCommerce or travel. Definitely worth listening in as Chaos Engineering was also put into the Top 5 Technologies to look into 2021 by CNCF.https://twitter.com/Ana_M_Medinahttps://www.spreaker.com/user/pureperformance/why-you-should-look-into-chaos-engineerihttps://twitter.com/CloudNativeFdn/status/1329863326428499971

When moving to microservice architectures its time to re-think continuous delivery. Just as many software services rely on a core data analytics engine to make better automated decisions we need to apply the same for continuous delivery. We can assess the risk of every microservice deployment based on data from production and the desired change of configuration. We can assess the potential blast radius and mitigate it through modern delivery options such as blue/green, canaries or feature flags.Tracy Ragan, Creator & CEO of DeployHub, CDF board member and DevOps Institute Ambassador shares her thoughts on why we need to move to smarter data-driven delivery pipelines. Tracy (@TracyRagan) gives us insights into why not every microservice is created equal and what approaches we can take to better control updates that contain multiple microservice updates.Also make sure to check out their latest project Ortelius and take Tracy up on a virtual coffee chat as discussed in our podcast!https://www.linkedin.com/in

K8s enables organizations to more easily deploy their containerized solutions as it takes away a lot of the operational tasks which are built-into k8s. This in theory means that you can run your software anywhere and provide it as SaaS offering or deploy it behind corporate firewalls for those customers that demand an on-premise installation.In this episode we have Marc Campbell, Founder and CTO of Replicated, where they help the k8s community to deliver and manage apps on k8s anywhere. For anyone looking into running their apps on k8s you will learn the challenges of Day 1 (delivery, install) and Day 2 (operation, monitoring, troubleshooting) operations. Marc shares common performance and scalability challenges and how to prepare for them during development.In this episode we have Marc Campbell, Founder and CTO of Replicated, where they help the k8s community to deliver and manage apps on k8s anywhere. For anyone looking into running their apps on k8s you will learn the challenges of Day 1 (delivery, insta

Stefan Frandl, Development Director, has a single digit employee number at Dynatrace and therefore seen a lot of agile transformation over the past 15 years – growing from a startup in Linz, Austria to now 800+ engineers across globally distributed labs. A visit to several “unicorns” such as Google, Facebook and Slack triggered the latest agile transformation.In this episode Stefan walks us through the implementation of the changes we discussed with Andrea Holl in her episode on “Scaling Agile at Dynatrace”. He shares the challenges around growing responsibilities of team leads, work left half-finished, overhead on hand-over and cross team collaboration. He then introduces us to the current structure and processes at Dynatrace such as Team Captains, Product Owners and Agile Advocates as well as Dev Directors and Lead Product Engineers. While Dynatrace has seen many benefits already, the journey is still ongoing as Dynatrace is continuously rethinking and improving the way we work and provide value to our cust

SAFE, LESS or the Spotify Model? Which scaled agile method to apply for your transformation? Or are you unique enough like 44% of organizations based on a European research that are defining their own scaled agile approach to transform successfully?In this episode we sit down with Andrea Holl, Agile Coach at Dynatrace, and let her walk us through the different scaled agile frameworks. She discusses the pros and cons and why many organizations – including Dynatrace – are coming up with their own approaches. For Dynatrace it was about taking the best from the proven frameworks but adapting them to allow us continue or core cultural values such as full autonomy to teams and flexibility of tools and processes.If you are on the brink of a transformation make sure to listen to Andrea and how she and her teams have approached that transformational project!https://www.linkedin.com/in/andrea-elisabeth-holl-b2255a112/https://www.scaledagileframework.com/https://less.works/https://blog.crisp.se/wp-content/uploads/2012/1

Daylight savings can bring chaos to systems such as rogue processes consuming CPU or memory and therefore impact your critical systems. The question is: how do you systems react to this chaos? How can you test for this? And how can you make your systems more resilient against this chaos?In this episode we talk with Ana Margarita Medina, Chaos Engineer at Gremlin. In her previous job, Ana (@Ana_M_Medina) was a Site Reliability Engineer at Uber where she helped coping with the “chaos” on New Years Eve or Halloween. Ana gives us great insights into the discipline of Chaos Engineering, that its really about running controlled experiment and that everyone can get started that has an interest in contributing to more resilient systems.Here the additional links we promised during the recording: Drift into failure, Chaos Engineering Community, Chaos Engineering and System Resilience in Practice.https://www.linkedin.com/in/anammedina/https://twitter.com/Ana_M_Medinahttps://eng.uber.com/nye/https://www.amazon.com/Drift-

We are sitting down with Sebastian Scheele (@sscheele), CEO and co-founder of Kubermatic, to discuss the challenges organizations have as they are moving their workloads to k8s and realize that managing, scaling and operating k8s is not getting easier the more k8s clusters you allow your application teams to spin up or down. We learn more about the Kubermatic Kubernetes Platform, the Open Source Project, which centrally manages the global automation of thousands of Kubernetes clusters across multi-cloud, on-prem and edge with unparalleled density and resilience.Thanks Sebastian for answering all the questions we threw at you – questions we have received from many organizations that are moving to k8s but get surprised about the complexity as it comes to properly operating and managing k8s.Sebastian Scheele Twitterhttps://twitter.com/sscheeleKubermatic Kubernetes Platformhttps://github.com/kubermatic/kubermatic

Keptn is now a CNCF sandbox project bringing a new event-driven approach to continuous delivery and operations. While many are just hearing about Keptn the first time, it is interesting to learn more about how it started, which challenges the team ran into, what they learned about K8s, and running an open-source project. We therefore invited Johannes Braeuer (@braeuer_j) and Andreas Grimmer (@grimmer_andreas) – both Keptn project maintainers and contributors – who have been working on the Keptn project since its inception.Especially for groups that want to start open-source projects or are on the brink of deciding pro or con Kubernetes should listen until the end as Johannes and Andreas tell us what they would do differently now if they would start today based on the learnings from the past 18 months.If you want to join the Keptn community, make sure to star our GitHub project, join the Slack channel, and join our regular community meetings!Keptnhttps://keptn.sh/Johannes Bräuer on Twitterhttps://twitter.com/b

Getting visibility into .NET code whether it runs on a developer machine, on a windows server on-premise or as a serverless function in the cloud is the day2day job of Georg Schausberger (@BombadilThomas) and Bernhard Ruebl, part of the Dynatrace .NET Agent Team.In this podcast we hear firsthand about the challenges in bringing observability, monitoring and distributed tracing to the .NET ecosystem. They give us insights about their continued effort to reduce startup and runtime overhead, the innovation that comes out of Microsoft as they are moving towards open standards and the noble automated approach to always validated things don’t break monitored code with the constant update of libraries and frameworks.We also got both to talk about their developer experience when working with commercial tools such as Dynatrace and its PurePath technology as well as open source tools when analyzing and debugging their own code or helping users figure out what’s wrong with their code.In the talk both mentioned other too

Successful Cloud Migrations, large scale Kubernetes & OpenShift deployments, making billions of data points actionable and enterprise-wide Citrix & SAP monitoring. These are some of the projects Kayan Hales, Technical Manager at Dynatrace, and her colleagues at Dynatrace ONE help enterprise customers around the world to implement every day.We sat down with Kayan as we wanted to learn what really matters to many large organizations as they embark on automating monitoring into their hybrid multi-cloud environments. While we constantly talk about cloud native and microservices it was interesting to hear what the global team of Dynatrace experts is doing on a day-2-day basis. Kayan gives us insights how important it is to think about meta data, tagging strategies and automation before large scale rollouts and that one of the first question you need to ask is: who needs what type of data at which time through which channels.https://www.linkedin.com/in/kayanhales/https://www.dynatrace.com/services-support/d

Why do some organizations still see performance testing as a waste of time? Why are we not demanding the same level of performance criteria for SaaS-based solutions as we do for in-house hosted services? Why are many organizations just validating performance to be “within specification” vs “holistically optimized”?In this episode we have invited James Pulley (@perfpulley), Performance Veteran and PerfBytes News of the Damned host, to discuss who organizations can level up from performance testing to true performance engineering. He also shares his approaches to analyzing performance issues and gives everyone advice on what to do to start a performance practice in your organization.https://www.linkedin.com/in/jameslpulley3/https://www.perfbytes.com/p/news-of-damned.html

Imagine a future where we deploy every code change directly into production because feature flags eliminated the need for staging. Feature flags allow us to deploy any code change, but only launch the feature to a specific set of users that we want to expose to new capabilities. Monitoring the usage and the impact enables continuous experimentation: optimizing what is not perfect yet and throw away features (technical debt) that nobody really cares about. So – what are feature flags?We got to chat with Heidi Waterhouse (@wiredferret), Developer Advocate at LaunchDarkly (https://launchdarkly.com/), who gives as a great introduction on Feature Flags, how organizations actually define a feature and why it is paramount to differentiate between Deploy and Launch. We learn how to test feature flags, what options we have to enable features for a certain group of users and how important it is to always include monitoring. IF you want to learn more about feature flags check out http://featureflags.io/. If you want to

Adrian Hornsby (@adhorn) has dedicated his last years helping enterprises around the world to build resilient systems. He wrote a great blog series titled “Patterns for Resilient Architectures” and has given numerous talks about this such as Resiliency and Availability Design Patterns for the Cloud at DevOne in Linz earlier this year.Listen in and learn more about why resiliency starts with humans, why we need to version everything we do, why default timeouts have to be flagged, how to deal with retries and backoffs and why every distributed architect has to start designing systems that provide different service levels depending on the overall system health state.Links:Adrian on Twitter: https://twitter.com/adhornMedium Blog Post: https://medium.com/@adhorn/patterns-for-resilient-architecture-part-1-d3b60cd8d2b6Adrian's DevOne talk: https://www.youtube.com/watch?v=mLg13UmEXlwDevOne Intro video: https://www.youtube.com/watch?v=MXXTyTc3SPU