Difference between revisions of "GC Enterprise Architecture/Standards/Technology Architecture"
Jump to navigation
Jump to search
| Line 36: | Line 36: | ||
<!-- COLUMN 2 STARTS: --> | <!-- COLUMN 2 STARTS: --> | ||
| − | <span style="font-size: 1.5em;"><b>Security Architecture>></b></span> | + | <span style="font-size: 1.5em;">[https://wiki.gccollab.ca/GC_Security_and_Privacy_Enterprise_Architecture <b>Security Architecture>></b>]</span> |
<!-- COLUMN 2 ENDS: --> | <!-- COLUMN 2 ENDS: --> | ||
Revision as of 18:18, 6 March 2019
| 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. |
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
