514
edits
Important: The GCConnex decommission will not affect GCCollab or GCWiki. Thank you and happy collaborating!
Changes
Jump to navigation
Jump to search
GC Enterprise Architecture/Standards/Technology Architecture (view source)
Revision as of 18:07, 6 March 2019
, 18:07, 6 March 2019no edit summary
Line 21:
Line 21:
<b>Use Cloud first</b>+<b>Design for Performance, Availability, and Scalability</b>+
<!-- 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
