The Mindset of an Architect (IT, Solution, Cloud, Enterprise)
The primary goal is to make decisions based on business requirements, company goals, and functional & non-functional requirements while ensuring the systems they design can operate within the confinements of scalability, reliability, and availability with optimal cost and maintainability. An architect bridges the gap between the infrastructure, business, and development and communicates to all parties what decisions have been made and why.
These decisions are carefully made by analyzing the benefits and trade-offs within the constraints of the business requirements, company goals, and non-functional and technical requirements.
Their technical expertise is considered wide-ranging, with a semi-shallow-to-midrange depth of technical knowledge. They are expected to have a broad knowledge of infrastructure, software development, DevOps automation, and subject domain knowledge, while their core depth of knowledge and expertise is understanding the design patterns, what problems they can solve, and the benefits and trade-offs between them.
