Architecture refers to the fundamental structures of a system and the discipline of creating such structures and systems. Each structure is made of elements, relations among elements, and the properties of both elements and relations.

In fact, architecture is very much about application plumbing. What kinds of fixtures (components) do we need, how do we connect them (message passing, events, APIs, etc.), and how can they be deployed (monolithic, networked, or combinations of both), operated, and managed.

Design is more about the specific components (sinks, faucets, kitchens, bathrooms, drains) and where they are placed and connected in order to build a house for a specified set of needs.

Effective architectural decisions enable the creation of resilient, agile, and durable application designs that can be implemented, deployed and operated, and maintained and enhanced more economically.

I have noticed, in my 50-year career building software systems, that most organizations have difficulty understanding the difference between architecture and design and take the "ready, fire, aim" approach to application building — paying a serious economic penalty during the life span of the resulting applications.