Continuing our relentless cataloging of architectural styles, in this episode we cover the service-based architecture. This is the only style in the book with a bespoke name, created by Mark and Neal, because it appeared in the wild so often as a pragmatic compromise on the extremes of microservices. In this episode, we describe the origins of the style, untangle the name from other architectures that include the word "service", and discuss trade-offs and ramifications beyond what we covered in the book, leading to a wide-ranging conversation.

Continuing our catalog of architectural styles, in this episode we cover the Microkernel architecture. Sometimes also known as a plug-in architecture, we introduce the idea of "microkernality" in this episode and talk about the myriad ways this architecture style appears in the real world. We cover a lot of information in this episode, expanding on the material in the book chapter.

Continuing our exploration of architecture styles, this month we go deep on the Pipeline (or Pipes and Filters) Style. This episode explores different types of filters, uses of this architecture, and how it differs from other similar styles.

This is the first of many chapters that each do a deep-dive on a particular architecture style; in this chapter, we start with the layered monolithic architecture, also known by many as the default architecture. We describe the topology, communication, data strategies, and philosophy underlying this style. We also point to ways to govern this style and how to adapt the style without breaking it.

The outcome of the architectural characteristics and logical component analysis we've been undertaking over the last few chapters is for an architect to choose an appropriate architecture style most suitable for the problem and capabilities we must build to be successful. Thus, this chapter starts a deep-dive on the most popular generic architecture styles that architects should be aware of. This chapter separates the concept of style versus pattern and describe how we'll tackle each fundamental style.

For the past few chapters/episodes, we've been delving into the analysis and definition of architectural characteristics, one of the two key structural design activities for software architects. In this chapter, we cover the other aspect of structural design in defining logical components, the building blocks of most software architectures. These define the behavior of the system, and we talk about some techniques and challenges in understanding the problem domain and translating it to software structure.

In this episode, we cover one of the key indicators for architects to answer one of the first questions they must consider--should they choose a monolithic or distributed architecture? Understanding and applying the scope of architectural characteristics is one of the keys to properly choosing most applicable solution. As usual, we cover details and background from the chapter and answer questions from the recording audience.

In this episode, we cover the critical topic of how architects can govern the architectural characteristics they identified. Architects are responsible for both identifying architectural characteristics, but should also ensure that they check on them to make sure the aspirational goal is manifesting. For example, if the team has a goal of 50ms First Contentful Paint for responsiveness, how can you determine if you've achieved that goal? As always, we cover some details and background from the chapter, and answer some live questions.