In their upcoming book, Software Architecture: The Hard Parts, Neal Ford and Mark Richards explain that every architectural decision involves trade-offs, and provide guidance on how to evaluate those trade-offs. In this episode of the InfoQ Podcast, co-host Thomas Betts spoke with Neal and Mark about the role of a software architect and the skills necessary to be successful. One of the hardest parts is recognizing that there are no right or wrong answers, or easy decisions, and this can be especially challenging for those who come from a programming background.

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

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

Upcoming Virtual Events - https://events.infoq.com/

InfoQ Live:
https://live.infoq.com/
- September 21, 2021
- October 19, 2021

QCon Plus online conference:
https://plus.qconferences.com/
- November 1-12, 2021

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

InfoQ Podcast

Transcript

Neal Ford and Mark Richards - Software Architecture: The Hard Parts

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

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.

Neal Ford and Mark Richards - Software Architecture: The Hard Parts

InfoQ

Related tracks