PurePerformance

16 years and still growing! Not every open source project has the track history of Spring (www.spring.io), a framework for building modern applications for the java runtime.Juergen Hoeller (@springjuergen), creator of the Spring framework, gives us insights into how he and his team have grown Spring to where it is now. We learn how they have built a developer community, how they deal with feedback, why its important to interact with your users on a regular basis and where the road is heading. Juergen also shares insights on topics such as scalability, performance, concurrency of the framework as well as how the rise of new java runtimes and distributions still keeps him excited about the future of Spring.If you want to learn more visit the Spring Framework’s GitHub project and make sure to read up on the latest blogs on https://spring.io/blog/https://spring.io/https://twitter.com/springjuergenhttps://github.com/spring-projects/spring-framework/

Are you analyzing the dependency between change frequency, technical complexity, and growth and length of code change hotspots? You should as it helps you with tackling technical debt and risk assessment the right way!In this podcast Adam Tornhill (@AdamTornhill) explains how he is applying data science and forensic approaches on data we all have in our organization such as: GIT commit history, ticket stats, static & dynamic code analysis, monitoring data … He is giving us insights in detecting code hotspots and how we can use leverage this data in areas such as risk assessment, the social side of code changes as well as explaining to business why working on technical debt is going to improve time to market.Also make sure to check out CodeScene: A powerful visualization tool that uses Predictive Analytics to find social patterns and hidden risks in your codeAdam Tornhill on Twitterhttps://twitter.com/AdamTornhillAdam Tornhill's bloghttps://www.adamtornhill.com/CodeScenehttps://www.empear.com

Are you analyzing the dependency between change frequency, technical complexity, and growth and length of code change hotspots? You should as it helps you with tackling technical debt and risk assessment the right way!In this podcast Adam Tornhill (@AdamTornhill) explains how he is applying data science and forensic approaches on data we all have in our organization such as: GIT commit history, ticket stats, static & dynamic code analysis, monitoring data … He is giving us insights in detecting code hotspots and how we can use leverage this data in areas such as risk assessment, the social side of code changes as well as explaining to business why working on technical debt is going to improve time to market.Also make sure to check out CodeScene: A powerful visualization tool that uses Predictive Analytics to find social patterns and hidden risks in your codeAdam Tornhill on Twitterhttps://twitter.com/AdamTornhillAdam Tornhill's bloghttps://www.adamtornhill.com/CodeScenehttps://www.empear.com

Did you know that Distributed Tracing has been around for much longer than the recent buzz? Do you know the history and future of OpenCensus, OpenTracing, OpenTelemetry and TraceContext? Listen to this podcast where we chat with Sonja Chevre, Technical Product Manager at Dynatrace, and Daniel Khan, Technical Evangelist at Dynatrace, about the past, current and future state of distributed tracing as a standard.OpenTelemetryhttps://opentelemetry.io/OpenCensushttps://opencensus.io/OpenTracinghttps://opentracing.io/TraceContexthttps://www.dynatrace.com/news/blog/distributed-tracing-with-w3c-trace-context-for-improved-end-to-end-visibility-eap/

Did you know that Distributed Tracing has been around for much longer than the recent buzz? Do you know the history and future of OpenCensus, OpenTracing, OpenTelemetry and TraceContext? Listen to this podcast where we chat with Sonja Chevre, Technical Product Manager at Dynatrace, and Daniel Khan, Technical Evangelist at Dynatrace, about the past, current and future state of distributed tracing as a standard.OpenTelemetryhttps://opentelemetry.io/OpenCensushttps://opencensus.io/OpenTracinghttps://opentracing.io/TraceContexthttps://www.dynatrace.com/news/blog/distributed-tracing-with-w3c-trace-context-for-improved-end-to-end-visibility-eap/

In 2018 Adrian Cockcroft was quoted with: “Chaos Engineering is an experiment to ensure that the impact of failures is mitigated”! In 2019 we sit down with one of his colleagues, Adrian Hornsby (@adhorn), who has been working in the field of building resilient systems over the past years and who is now helping companies to embed chaos engineering into their development culture. Make sure to read Adrian’s chaos engineering blog and then listen in and learn about the 5 phases of chaos engineering: Steady State, Hypothesis, Run Experiment, Verify, Improve. Also learn why chaos engineering is not limited to infrastructure or software but can also be applied to humans.Adrian on Twitter:https://twitter.com/adhornAdrian's Blog:https://medium.com/@adhorn/chaos-engineering-ab0cc9fbd12a

In 2018 Adrian Cockcroft was quoted with: “Chaos Engineering is an experiment to ensure that the impact of failures is mitigated”! In 2019 we sit down with one of his colleagues, Adrian Hornsby (@adhorn), who has been working in the field of building resilient systems over the past years and who is now helping companies to embed chaos engineering into their development culture. Make sure to read Adrian’s chaos engineering blog and then listen in and learn about the 5 phases of chaos engineering: Steady State, Hypothesis, Run Experiment, Verify, Improve. Also learn why chaos engineering is not limited to infrastructure or software but can also be applied to humans.Adrian on Twitter:https://twitter.com/adhornAdrian's Blog:https://medium.com/@adhorn/chaos-engineering-ab0cc9fbd12a

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

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

Susanne Kaiser (@suksr) has transformed her company from monolith on-premise into a SaaS solution running on a microservice architecture: Successfully! Nowadays she consults companies that need to find their “core domain”, break up and re-fit their architectures and organizational structure in order to truly get the benefit of microservices.In this podcast you learn which questions you need to ask before starting a microservice project, how to find your true “core domain”, how to restructure not only your code but also organization and you get exposed to the concept of Wardley Maps which help you decide what to build vs what to outsource in order to deliver value to your end users the most efficient way.Links:Susannne on Twitter - https://twitter.com/suksrDevOne Conference Page - https://devexperience.ro/speakers/susanne-kaiser/Wardley Maps Microservices presentation - https://www.slideshare.net/SusanneKaiser3/preparing-for-a-future-microservices-journey-with-wardley-maps

Susanne Kaiser (@suksr) has transformed her company from monolith on-premise into a SaaS solution running on a microservice architecture: Successfully! Nowadays she consults companies that need to find their “core domain”, break up and re-fit their architectures and organizational structure in order to truly get the benefit of microservices.In this podcast you learn which questions you need to ask before starting a microservice project, how to find your true “core domain”, how to restructure not only your code but also organization and you get exposed to the concept of Wardley Maps which help you decide what to build vs what to outsource in order to deliver value to your end users the most efficient way.Links:Susannne on Twitter - https://twitter.com/suksrDevOne Conference Page - https://devexperience.ro/speakers/susanne-kaiser/Wardley Maps Microservices presentation - https://www.slideshare.net/SusanneKaiser3/preparing-for-a-future-microservices-journey-with-wardley-maps

To service mash or not? That’s a good question! Not every architecture and project needs a service mesh but for running distributed microservices architectures service mashes provide a lot of essential features such as service discovery, traffic routing, security, observability ..We invited Matt Turner (@mt165), CTO at Native Wave, to tell us all we need to know about service mashes. We get a deep dive into Istio, one of the most popular current service mashes, the architecture and how the individual components such as Envoy, Pilot, Mixer and Citadel work together. We also chat about the tradeoff between performance, latency, throughput and service mash capabilities. If you want to learn more make sure to check out Matt’s online content such as blogs and recorded conference presentations on https://mt165.co.uk/.Native Wave https://nativewave.io/Istio vs. Linkerd CPU Overhead Benchmarks by Michael Kipper Initial Observations: https://medium.com/@michael_87395/benchmarking-istio-linkerd-cpu-c36287e32781 Second Analysis: https://medium.com/@michael_87395/benchmarking-istio-linkerd-cpu-at-scale-5f2cfc97c7fa

To service mash or not? That’s a good question! Not every architecture and project needs a service mesh but for running distributed microservices architectures service mashes provide a lot of essential features such as service discovery, traffic routing, security, observability ..We invited Matt Turner (@mt165), CTO at Native Wave, to tell us all we need to know about service mashes. We get a deep dive into Istio, one of the most popular current service mashes, the architecture and how the individual components such as Envoy, Pilot, Mixer and Citadel work together. We also chat about the tradeoff between performance, latency, throughput and service mash capabilities. If you want to learn more make sure to check out Matt’s online content such as blogs and recorded conference presentations on https://mt165.co.uk/.Native Wave https://nativewave.io/Istio vs. Linkerd CPU Overhead Benchmarks by Michael Kipper Initial Observations: https://medium.com/@michael_87395/benchmarking-istio-linkerd-cpu-c36287e32781 Second Analysis: https://medium.com/@michael_87395/benchmarking-istio-linkerd-cpu-at-scale-5f2cfc97c7fa

Keptn (@keptnProject) is an open source control plane for Kubernetes enabling continuous delivery and automated operations. In this session we chat with Dirk Wallerstorfer (@wall_dirk) who is leading the keptn development team. We learn from Dirk why they choose knative as serverless framework to let keptn connect to other DevOps tools in the toolchain, how the event driven architecture works, which use cases are supported and where the road is heading.If you are interested also check out our Getting Started with keptn YouTube Tutorial, join the keptn slack channel, keep an eye at the keptn community and give feedback after trying out keptn yourself by following the following installation instructions: https://keptn.sh/docs/Links:keptn on Twitter - https://twitter.com/keptnProjectDirk on Twitter - https://twitter.com/wall_dirkknative - https://cloud.google.com/knative/Keptn Video - https://www.youtube.com/watch?v=0vXURzikTacKeptn Slack - https://keptn.slack.com/join/shared_invite/enQtNTUxMTQ1MzgzMzUxLTcxMzE0OWU1YzU5YjY3NjFhYTJlZTNjOTZjY2EwYzQyYWRkZThhY2I3ZDMzN2MzOThkZjIzOTdhOGViMDNiMzIKeptn Community - https://github.com/keptn/communityKeptn Docs - https://keptn.sh/docs/

Keptn (@keptnProject) is an open source control plane for Kubernetes enabling continuous delivery and automated operations. In this session we chat with Dirk Wallerstorfer (@wall_dirk) who is leading the keptn development team. We learn from Dirk why they choose knative as serverless framework to let keptn connect to other DevOps tools in the toolchain, how the event driven architecture works, which use cases are supported and where the road is heading.If you are interested also check out our Getting Started with keptn YouTube Tutorial, join the keptn slack channel, keep an eye at the keptn community and give feedback after trying out keptn yourself by following the following installation instructions: https://keptn.sh/docs/Links:keptn on Twitter - https://twitter.com/keptnProjectDirk on Twitter - https://twitter.com/wall_dirkknative - https://cloud.google.com/knative/Keptn Video - https://www.youtube.com/watch?v=0vXURzikTacKeptn Slack - https://keptn.slack.com/join/shared_invite/enQtNTUxMTQ1MzgzMzUxLTcxMzE0OWU1YzU5YjY3NjFhYTJlZTNjOTZjY2EwYzQyYWRkZThhY2I3ZDMzN2MzOThkZjIzOTdhOGViMDNiMzIKeptn Community - https://github.com/keptn/communityKeptn Docs - https://keptn.sh/docs/