ConceptsPrinciples4Interview

To best support continuously-delivering, autonomous teams, a software architect has to avoid being a blocker by trying to make all architectural decisions. In this episode of the podcast, Thomas Betts talks to Andrew Harmel-Law about how an advice process allows anyone to make an architectural decision, once they’ve had necessary conversations and properly documented their decision.

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

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

Upcoming Virtual Events - events.infoq.com/

QCon London:
qconlondon.com/
- April 4-6, 2022 / London, UK

QCon Plus: 
plus.qconferences.com/
- May 10-20, 2022
- Nov 29 - Dec 9, 2022

QCon San Francisco
qconsf.com/
- Oct 24-28, 2022

InfoQ Live:
live.infoq.com/
- Feb 22, 2022
- June 21, 2022
- July 19, 2022
- August 23, 2022

Follow InfoQ:
- Twitter: twitter.com/infoq
- LinkedIn: www.linkedin.com/company/infoq/
- Facebook: www.facebook.com/InfoQdotcom/
- Instagram: @infoqdotcom
- Youtube: www.youtube.com/infoq

InfoQ Podcast

Transcript

The Architecture Advice Process with Andrew Harmel-Law

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

Show Notes

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

So, after far too long a hiatus, we’re back on the Magpie Talkshow for a one-off episode where I interview Kafka creator and Confluent CEO Jay Kreps. 

I’ve been doing a small amount of work with Confluent recently, and through this I got the chance to meet Jay, and I thought he’d make a great guest for the show. So in this episode we’re going to learn about Jay’s own journey in the tech industry, as well as diving into the mindset behind Kafka and where you might want to use it.

There are a couple of firsts in this episode. Firstly, it was recorded remotely via video conferencing - I think the audio quality is pretty good, largely thanks to the use of zencaster. I did however have to do more editing than usual but I’m pretty happy with how it turned out. Secondly We’re also going to be sharing a video of our chat over on confluent's website, and I’ll update this post with a link once it’s available.

I do have to apologise for the sporadic nature of the episodes I’m putting out but as is often the case, life get’s in the way. In between our last episode and this one I setup my own company, and left australia for London, where I am currently based. I still plan to publish the occasional episode from time to time, so please do stay subscribed to the feed. Hopefully if things settle down a bit I may get back to a more regular posting schedule!

Jay and I talked about a number of things on the podcast, but the main one I wanted to highlight is previous guest Ben Stopford’s really interesting posts on using Kafka for sharing data between microservices. There are some fascinating ideas there which I think can solve problems many of us face when creating finer-grained distributed systems. You can find Ben's posts here: https://www.confluent.io/blog/author/ben/.

Anyway, I hope you enjoy the show!

Magpie Talkshow Episode 23 - Jay Kreps

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Josh Evans, former engineering manager at Netflix on how Netflix does DevOps and the freedom and responsibility culture that undermines their way of working. 

Why listen to this podcast:

•	There are many interpretations of the term DevOps, it is a useful shorthand for a wide variety of technologies and approaches 
•	“You build it, you run it” is the concrete application of the freedom and responsibility culture
•	When building a platform tool make it so easy to use that the product teams are not tempted to try and build something for themselves
•	Product teams are free to experiment and learn, which can feel chaotic and is a valuable part of the freedom and responsibility culture
•	The value of blameless and safe incident reviews – the goal is to learn and find patterns and use that information to present whole classes of failure from happening in the future
•	Don’t view the value stream in a fragmented way – see the whole end to end system with all its interactions and dependencies and optimize the system as a cohesive whole rather than different tools and domains

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

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

Subscribe: www.youtube.com/infoq
Like InfoQ on Facebook: bit.ly/2jmlyG8
Follow on Twitter: twitter.com/InfoQ
Follow on LinkedIn: www.linkedin.com/company/infoq
Want to see extented shownotes? Check the landing page on InfoQ: http://bit.ly/2mtCIr1

Josh Evans on DevOps at Netflix

In this episode of the O’Reilly Programming Podcast, we revisit our June 2017 conversation with Sam Newman, presenter of the O’Reilly video course The Principles of Microservices and the online training course From Monolith to Microservices. He is also the author of the book Building Microservices: Designing Fine-Grained Systems.

Sam Newman on Building Microservices

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.

The Architecture Advice Process with Andrew Harmel-Law

InfoQ

Related tracks