Technical Architecture

There are many views about the different roles in architecture. Many of these views can appear quite political but the clearest steer you can get in my view is to consider Technical architecture to be only concerned with defining infrastructure or code that will meet a specific set of operating criteria.

It is equally helpful to understand that a technical architect has no interest in a business goal or strategy or a user or customer of the system(s), but rather it’s capacity, resilience and capabilities.
In an enterprise a Technical architect may specify everything form basic networking hardware upwards and decide which servers run what and how they communicate, but have little interest in the type of business functions being supported.  A technical architect in a software development team may be concerned about the libraries, components , middleware, protocols and the methods of testing and deployment, but have only a modest interest in what function each part is carrying out in customer or user terms.

The “Explainned series” is planned to build into a trustworthy collection of explanations and commentaries that can be trusted to tell the story straight without any bias and attempt to make the subjects accessible to the layman. The latter is not always easy as some of these terms refer to genuinely complex subject matter, while others are simply too vague to pin down (there’s another word for that).
If you want an answer on something and you can’t find it easily, please use the comments section to just ask and I will apreciate not having to research the next topic.