GC Enterprise Architecture/Standards/Technology Architecture
< GC Enterprise Architecture | Standards
Revision as of 17:15, 6 March 2019 by Gita.nurlaila (talk | contribs)
Home | EA standards | EARB Endorsements | EA Artifacts | Working Groups | GC EARB | Other References |
This page is a work in progress. We welcome your feedback. Please use the discussion page for suggestions and comments. When the page is approved and finalized, we will send it for translation. |
Security Architecture>> |
4. Technology Architecture
This is a definition for GC Technology Enterprise Architecture
Use Cloud first
- Enforce this order of preference: Software as a Service (SaaS) first, then Platform as a Service (PaaS), and lastly Infrastructure as a Service (IaaS)
- Enforce this order of preference: Public cloud first, then Hybrid cloud, then Private cloud, and lastly non-cloud (on-premises) solutions
- Design for cloud mobility and develop an exit strategy to avoid vendor lock-in
Design for Performance, Availability, and Scalability
- Design for resiliency
- Ensure response times meet user needs, and critical services are highly available
- Support zero-downtime deployments for planned and unplanned maintenance
- Use distributed architectures, assume failure will happen, handle errors gracefully, and monitor actively