Architecture considerations

By | March 29, 2018

Below are the concerns of the architect. There  are so many concerns because architecture can be applied to so many different industries and levels within an organization.

  • Use case concerns
    • *-ability (Scalability, availability, reliability, perform-ability)
    • Concurrent load – many how concurrent users?
    • Volume – how much data?
    • Interaction types (Real-time response, Delay response)
    • Persistence & Retrieval
  • Cross cutting concerns.
    • Security
    • Diagnostics
    • Caching
    • Error handling
    • Validation
    • Transactions
  • Business considerations
    • Processes
    • Methodologies
  • Technical considerations
    • Technology
      • Hardware
      • Commercial / Open source software?
      • What type of technology to use where.
    • Logical processes
      • Process boundaries
      • Identities
      • Transactions
    • Coupling
    • Identification of  requirement volatiles
    • Existing Code complexity
    • Deployment & Infrastructure (On prem, IAAS & PAAS)
  • Risks & Limitations
    • Current Architecture
    • Legal (Are there any laws that must be considered for the region of deployment like GDPR)
    • Technology
    • Alternatives
    • HR (Staffing)
      • Skills to fulfill the planned tasks?
      • Political landscape – Regional and within the company.
    • Estimations (with assistance from Domain expert or Team lead)
      • Cost of failure or late delivery
  • Review of architecture in production.

Leave a Reply

avatar

This site uses Akismet to reduce spam. Learn how your comment data is processed.

  Subscribe  
Notify of