514
edits
Changes
GC Enterprise Architecture/Framework/TechnologyGuide (view source)
Revision as of 10:05, 25 February 2021
, 10:05, 25 February 2021no edit summary
* Cloud Assessment Framework
* Cloud Assessment Framework
* Summary of Cloud Access Scenarios and Usage Profiles
* Summary of Cloud Access Scenarios and Usage Profiles
* 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: software as a service (SaaS) first, then platform as a service (PaaS), and lastly infrastructure as a service (IaaS)
* Cloud Reference Architecture
* Cloud Reference Architecture
* Cloud Assessment Framework
* Cloud Assessment Framework
* fulfill cloud services through SSC Cloud‑Brokering Services
* fulfill cloud services through SSC Cloud‑Brokering Services
<b>Tools:</b>
<b>Tools:</b>
* Contact Cloud COE
* Contact Cloud COE
* enforce this order of preference: public cloud first, then hybrid cloud, then private cloud, and lastly non‑cloud (on‑premises) solutions
* enforce this order of preference: public cloud first, then hybrid cloud, then private cloud, and lastly non‑cloud (on‑premises) solutions
* The implementation of applications are not susceptible to latency issues, which may arise due to traffic moving through an additional circuit.
* The implementation of applications are not susceptible to latency issues, which may arise due to traffic moving through an additional circuit.
* The implementation of applications, which do not have voluminous transactions with an on-premises database or application.
* The implementation of applications, which do not have voluminous transactions with an on-premises database or application.
<b>Tools:</b>
<b>Tools:</b>
* Cloud Reference Architecture
* Cloud Reference Architecture
* Cloud Assessment Framework
* Cloud Assessment Framework
* design for cloud mobility and develop an exit strategy to avoid vendor lock‑in
* design for cloud mobility and develop an exit strategy to avoid vendor lock‑in
* Solution Architecture
* Solution Architecture
* Refer YDG GC EARB
* Refer YDG GC EARB
=== Design for performance, availability and scalability ===
=== Design for performance, availability and scalability ===
<b>Tools:</b>
<b>Tools:</b>
* non-functional requirements
* non-functional requirements
* support zero‑downtime deployments for planned and unplanned maintenance
* support zero‑downtime deployments for planned and unplanned maintenance
<b>Tools:</b>
<b>Tools:</b>
* non-functional requirements
* non-functional requirements
* use distributed architectures, assume failure will happen, handle errors gracefully, and monitor performance and behaviour actively
* use distributed architectures, assume failure will happen, handle errors gracefully, and monitor performance and behaviour actively
<b>Tools:</b>
<b>Tools:</b>
* non-functional requirements
* non-functional requirements
* establish architectures that supports new technology insertion with minimal disruption to existing programs and services
* establish architectures that supports new technology insertion with minimal disruption to existing programs and services
<b>Tools:</b>
<b>Tools:</b>
* non-functional requirements
* non-functional requirements
* control technical diversity; design systems based on modern technologies and platforms already in use
* control technical diversity; design systems based on modern technologies and platforms already in use
<b>Tools:</b>
<b>Tools:</b>
* non-functional requirements
* non-functional requirements
=== Follow DevSecOps principles ===
=== Follow DevSecOps principles ===
<b>Tools:</b>
<b>Tools:</b>
* CICP mesh
* CICP mesh
* ensure automated testing occurs for security and functionality
* ensure automated testing occurs for security and functionality