Changes

Jump to navigation Jump to search
m
no edit summary
Line 16: Line 16:  
     * 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)
Line 28: Line 29:  
     * 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
Line 35: Line 37:  
     <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
Line 45: Line 48:  
         * 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
Line 58: Line 61:  
     * Solution Architecture
 
     * Solution Architecture
 
     * Refer YDG GC EARB  
 
     * Refer YDG GC EARB  
 +
    
=== Design for performance, availability and scalability ===
 
=== Design for performance, availability and scalability ===
Line 69: Line 73:  
     <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
Line 80: Line 85:  
     <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
Line 89: Line 95:  
     <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
Line 96: Line 103:  
     <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
Line 104: Line 112:  
     <b>Tools:</b>
 
     <b>Tools:</b>
 
     * non-functional requirements
 
     * non-functional requirements
 +
    
=== Follow DevSecOps principles ===
 
=== Follow DevSecOps principles ===
Line 113: Line 122:  
     <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
514

edits

Navigation menu

GCwiki