Focus on quality attributes, which represent the key cross-cutting requirements that a good architecture should address.

In software-intensive systems, technical debt consists of design or implementation constructs that are expedient in the short term but that set up a technical context that can make future change more costly or impossible. Technical debt is a contingent liability whose impact is limited to internal system qualities—primarily, but not only,

As software engineers and architects our job is to try to use our technical and logical thinking skills to identify which is which and to challenge those that are not useful. Which activities help us to really be secure and which are outdated or simply useless “security theatre”? If we don’t do this then all security activities will be devalued and

Most commercial organizations face the following challenges when defining the architectures of their products: Focus on technology details rather than business context. Perception of architects as not delivering solutions or adding value. Inability of architectural practices to address the increase in speed of IT delivery and to adapt to modern

Consequently, we must design our systems with recovery from security incidents in our mind and must think about preventing the incidents in the first place. We discuss system resilience in Chapter 7, but from a security perspective, an important part of ensuring resilience is to work closely with the security specialists and SOC personnel while

For example, enterprise architecture boards make far fewer decisions than product-level governance boards. Note that the scope and significance of architectural decisions also increase with scale. However, most decisions that can impact an architecture are driven on the ground by development teams. The closer you get to implementation, the more

1: Architect products; evolve from projects to products. Architecting products is more efficient than just designing point solutions to projects and focuses the team on its customers. Principle 2: Focus on quality attributes, not on functional requirements. Quality attribute requirements drive the architecture. Principle 3: Delay design decisions

Continuous Architecture states that an architect is responsible for enabling the implementation of a software system by driving architectural decisions in a manner that protects the conceptual integrity of the software system.

Know your technical debt, the understanding and management of which is key for a sustainable architecture. Lack of awareness of technical debt will eventually result in a software product that cannot respond to new feature demands in a cost-effective manner.