Continuous profiling is collecting profiling data (think things like memory and CPU) all the time/throughout time in your production environment. Today on the podcast, Wes Reisz speaks with Frederic Branczyk, CEO of PolarSignals, a startup formed to enable continuous profiling leveraging eBPF. Wes and Frederic discuss the origin story of Polar Signals, eBPF (the enabling technology used by Polar Signals), Parca (the open-source system they built to collect continuous profiling data), and more, including things like FrostDB and why profiling data complements what we already have with our currenct observability stacks.

Read a transcript of this interview: https://bit.ly/3SpIcxj

Subscribe to our newsletters:
- The InfoQ weekly newsletter: https://bit.ly/24x3IVq
- The Software Architects’ Newsletter [monthly]: https://www.infoq.com/software-architects-newsletter/

Upcoming Events:

QCon San Francisco:
https://qconsf.com/
- Oct 24-28, 2022
- Oct 2-6, 2023

QCon Plus online: 
https://plus.qconferences.com/
- Nov 29 - Dec 9, 2022

QCon London 
https://qconlondon.com/
- March 26-31, 2023

Follow InfoQ:
- Twitter: https://twitter.com/InfoQ
- LinkedIn: https://www.linkedin.com/company/infoq
- Facebook: https://bit.ly/2jmlyG8
- Instagram: https://www.instagram.com/infoqdotcom/
- Youtube: https://www.youtube.com/infoq

Transcript

Frederic Branczyk on Continuous Profiling Leveraging eBPF

Jonas Bonér, CTO of LightBend and creator Akka, discusses using Akka when developing distributed systems. He talks about the Actor Model, and how every Microservice needs to be viewed as a system to be successful. 

Why listen to this podcast:

 - Akka is JVM-based framework design for developing distributed systems leveraging the Actor Model - an approach for writing concurrent systems that treat actors as universal primitives and the most successful model with abstraction has been streaming
 - Circuit breakers in Akka are a backup and retry policy; they protect you by capturing failure data and allow you to roll back 
 - Every Microservice needs to be viewed as a system, it needs to have multiple parts that run on different machines in order to function and be fully resilient - thus is a Microsystem
 - Two different trends have emerged when it comes to hardware and environments: one is the trend toward Multi-core, the is a movement toward virtualized environments and the cloud
 - Saga pattern of managing long running transactions in a distributed system fits very well with messaging style architectures

Notes and links can be found on: http://bit.ly/2kwB2eB

Akka
The Actor Model
When Akka and the Actor Model is the perfect choice
Circuit breakers patterns in distributed systems
Two trends toward Multi-core
Reactive Manifesto
Event Driven vs. Message Driven
Reactive Programming and Streams
Microliths to Microsystems
What do you have to get right before you start trying to deploy a distributed systems?
Working with ML / AI at Lightbend to understand tracing through distributed system
Saga Pattern

More on this:
Quick scan our curated show notes on InfoQ http://bit.ly/2kwB2eB

You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq

InfoQ Podcast

Show Notes

Jonas Bonér on the Actor Model, Akka, Reactive Programming, Microservices and Distributed Systems

Software engineers, architects and team leads have found inspiration to drive change and innovation in their team by listening to the weekly InfoQ Podcast. They have received essential information that helped them validate their software development map. We have achieved that by interviewing some of the top CTOs, engineers and technology directors from companies like Uber, Netflix and more. Over 1,200,000 downloads in the last 3 years.