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.