On Architecture

🦄 On Architecture

In on-premises enviroment, customer often maintain a technical architect team, this is a central team acts as an overlay other product or feature teams to ensure they are following the best practices. This is a core team of technology center that combined a lot of architect roles such as: Technial Architect (Infrastructure), Solution Architect, Data Architect, Networking Architect, and Security Architect. Normally, these teams use TOGAF or Zachman Framework as part of an enterprise architect capability.

AWS prefer to distribute capabilities into teams rather than having a central team with that capacity. There are risks when you choose to distributedecision making authority, for example, ensuring that teams are meeting internalstandards. We mitigate these risks in two ways.

  • First, we have practices that focus onenabling each team to have that capability, and we put in place experts who ensurethat teams raise the bar on the standards they need to meet.
  • Second, we implement mechanisms that carry out automated checks to ensure standards are being met.This distributed approach is supported by the Amazon leadership principles, andestablishes a culture across all roles that works back3 from the customer. Customer-obsessed teams build products in response to a customer need.

“Good intentions never work, you need good mechanisms to make anything happen” Jeff Bezos. Thismeans replacing humans best efforts with mechanisms (often automated) that check for compliance withrules or process.