Difference between revisions of "GC Enterprise Architecture/Standards/Technology Architecture"
Jump to navigation
Jump to search
Jana.jessome (talk | contribs) (Created page with "<!-- NAV --> {| class="FCK__ShowTableBorders" style="border-right: 0px; border-top: 0px; border-left: 0px; border-bottom: 0px; background-color: #3C6D9E" width="100%" align="c...") |
|||
| Line 21: | Line 21: | ||
<!-- NAV end --> | <!-- NAV end --> | ||
| − | {{Translation to follow}} | + | <i>{{Translation to follow}}</i> |
| + | <br> | ||
| + | <!-- Columns --> | ||
| + | {| width="100%" cellpadding="10" | ||
| + | |- valign="top" | ||
| + | | width="50%" style="color: blue;" | | ||
| + | |||
| + | <!-- COLUMN 1 STARTS: --> | ||
| + | <span style="font-size: 1.5em;"><b><<Application Architecture</b></span> | ||
| + | <!-- COLUMN 1 ENDS: --> | ||
| + | |||
| + | | width="50%" style="color: blue;" | | ||
| + | |||
| + | <!-- COLUMN 2 STARTS: --> | ||
| + | <span style="font-size: 1.5em;"><b>Security Architecture>></b></span> | ||
| + | <!-- COLUMN 2 ENDS: --> | ||
| + | |||
| + | |} | ||
| + | |||
| + | =4. Technology Architecture= | ||
| + | <br> | ||
This is a definition for GC Technology Enterprise 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: 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 | * 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 cloud mobility and develop an exit strategy to avoid vendor lock-in | ||
| − | + | ==Design for Performance, Availability, and Scalability== | |
* Design for resiliency | * Design for resiliency | ||
* Ensure response times meet user needs, and critical services are highly available | * Ensure response times meet user needs, and critical services are highly available | ||
* Support zero-downtime deployments for planned and unplanned maintenance | * Support zero-downtime deployments for planned and unplanned maintenance | ||
* Use distributed architectures, assume failure will happen, handle errors gracefully, and monitor actively | * Use distributed architectures, assume failure will happen, handle errors gracefully, and monitor actively | ||
Revision as of 18:07, 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. |
|
<<Application Architecture |
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
