In our second architecture styles chapter, we delve into the Domain-driven Design inspired cousin of the Layered architecture (our previous episode)--the Modular Monolith.

We describe what sets these two monolithic architectures apart, what the superpowers (and kryptonite) for this style, and when you would use it rather than a layered architecture.

And, as always, we answer the voluminous questions from our audience at the recording.

The main part of the Head First Software Architecture book is a catalog of architecture styles; this is the first of several chapters delving in the structure, communication, and all the other characteristics of named architectural styles, in this case, the Layered Architecture. We start with the traditional layered architecture as it is so common, and it has an easy to understand structure. We discuss its uses, how layered related to the domain, and limitations. For each architectural style, we also cover the Superpowers and Kryptonite for that style.

As architects, we often talk about patterns--contextualized solutions to problems. But we must also choose between architectural styles: named topologies that include component organization, logical (and sometimes physical) deployment, communication,and a host of other characteristics. In this episode, we distinguish between patterns and styles and answer some common questions.

Structural design in software architecture entails both architectural characteristics analysis and deriving logical component from the problem domain. This episode of the podcast delves into logical component analysis, some traps to avoid, and some different analysis techniques. And, as always, answer lots of questions that came up during the discussion.

Chapter Three of Head First Software Architecture covers our Two Laws of software architecture:
1) Everything in software architecture is a trade-off
2) Understanding why is more important than understanding how

In this episode, we discuss the origin of these two laws, why we consider them universal, and the (sometimes deep) implications of them for architects making trade-off decisions.

In this episode, we cover the first of the core four dimensions that make up software architecture: architectural characteristics. We discuss what they are and answer questions about derivation, composition, and a host of other factors required to understand this building block of structural design.

Covering the first chapter of Head First Software Architecture, this episode dives into the spectrum of differences between architecture and design. We also cover the four dimensions of software architecture, which forms the narrative scaffolding for the next few chapters: architectural characteristics, architectural decisions, logical components, and architectural styles.