The hard parts of software architecture

Thoughtworks Technology Podcast

Thoughtworks

Careers, Business, 907234, Technology

4.7 • 53 Ratings

🗓️ 7 October 2021

⏱️ 38 minutes

🔗️ Recording | iTunes | RSS

🧾️ Download transcript

Summary

In today’s modern distributed systems are by their very nature complex. The decisions you need to make — around the wiring of your services, what size should the services be, and how should they call one another — are uniquely complex. In Software Architecture: the hard parts, the authors explore the rough edges of software architecture and look at how you can effectively do trade analyses that work for you. We catch up with two of the book’s co-authors.

Transcript

Click on a timestamp to play from that location

0:00.0	Hello, everyone. My name is Rebecca Parsons, and I'm one of your recurring co-hosts on the ThoughtWorks
0:10.0	Technology podcast. And I'm here today with Neil Ford, who was not here as a co-host, but as a guest,
0:17.9	as well as Mark Richards. We have a podcast from a while ago where I spoke to the two of
0:24.6	them about their book, The Fundamentals of Software Architecture, and they're here today to talk to us
0:30.2	about their forthcoming book on architecture, The Hard Parts. Wow, the guest chairs in the studio are much more comfortable than the podcaster chair.
0:40.3	So this is really a treat.
0:42.3	So thanks for having us.
0:43.3	Yeah, thank you so much, Rebecca.
0:45.3	The first question that came to my mind when I heard Neil Starr talking about this book is,
0:52.3	okay, first, the title, the hard parts.
0:57.5	You just finished a really comprehensive book on the fundamentals of software architecture.
1:05.1	What more could there be?
1:07.3	What prompted you all to do yet another book talking about architecture and why scope it to
1:14.5	the hard parts? Well, it's a great question and a great obvious first question. And as we were
1:20.5	writing in the fundamentals book, we kept running into these problems that we would start diving into
1:26.1	and then realized, oh, no, this is a rabbit hole.
1:29.7	This is going to take forever to get into all of the different possibilities and tradeoffs
1:34.2	and this.
1:34.5	And so we started putting those aside and saying, well, we'll do that in some future book or
1:40.4	something.
1:41.0	And Mark is actually credited with coming up with his name because he said at one
1:44.6	point, hey, I know what we should call the next book, is architecture the hard parts because it's all
	...

Please login to see the full transcript.

Previous episode | Next episode

Disclaimer: The podcast and artwork embedded on this page are from Thoughtworks, and are the property of its owner and not affiliated with or endorsed by Tapesearch.

Generated transcripts are the property of Thoughtworks and are distributed freely under the Fair Use doctrine. Transcripts generated by Tapesearch are not guaranteed to be accurate.