GC Enterprise Architecture/Standards/Technology Architecture - Revision history

Nick.schonning: Use template header/footer

2020-07-24T19:30:17Z

Use template header/footer

Nick.schonning: Nick.schonning moved page GC Enterprise Technology Architecture to GC Enterprise Architecture/Standards/Technology Architecture

2020-07-24T18:43:05Z

Nick.schonning moved page GC Enterprise Technology Architecture to GC Enterprise Architecture/Standards/Technology Architecture

Nick.schonning: Close "i" tag

2019-08-27T14:29:29Z

Close "i" tag

Nick.schonning: Spike in more placeholders

2019-08-27T14:19:03Z

Spike in more placeholders

Nick.schonning: Sketch in some subbullets

2019-08-23T21:48:45Z

Sketch in some subbullets

Jana.jessome: Jana.jessome moved page GC Technology Enterprise Architecture to GC Enterprise Technology Architecture

2019-03-18T14:49:37Z

Jana.jessome moved page GC Technology Enterprise Architecture to GC Enterprise Technology Architecture

Gita.nurlaila at 22:18, 6 March 2019

2019-03-06T22:18:03Z

Gita.nurlaila at 22:15, 6 March 2019

2019-03-06T22:15:38Z

Gita.nurlaila at 22:07, 6 March 2019

2019-03-06T22:07:19Z

Jana.jessome: Created page with " {| class="FCK__ShowTableBorders" style="border-right: 0px; border-top: 0px; border-left: 0px; border-bottom: 0px; background-color: #3C6D9E" width="100%" align="c..."

2019-03-06T18:48:59Z

Created page with " {| class="FCK__ShowTableBorders" style="border-right: 0px; border-top: 0px; border-left: 0px; border-bottom: 0px; background-color: #3C6D9E" width="100%" align="c..."

New page

{| class="FCK__ShowTableBorders" style="border-right: 0px; border-top: 0px; border-left: 0px; border-bottom: 0px; background-color: #3C6D9E" width="100%" align="center"
|-
|-
| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="6%" | '''[[GC_Enterprise_Architecture|'''Home''']]'''

| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="11%" | '''[[Government_of_Canada_Architectural_Standards|'''EA standards''']]'''

| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="13%" | '''[[Past_Endorsed_Architectural_Decisions|'''EARB Endorsements''']] '''

| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="11%" | '''[[Enterprise_Architecture_Artifacts|'''EA Artifacts''']] '''

| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="12%" | '''[[Architecture_Discussions|'''Working Groups''']] '''

| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="11%" | '''[[GC EARB|'''GC EARB''']] '''

| style="border-right: white 1px ridge; padding-right: 0px; padding-left: 0px; padding-bottom: 2px; padding-top: 2px; text-align: center; font-family: (Cooper black); font-size: 13pt" width="9%" | '''[[Monitoring_Architectural_Implementation|'''Other References''']] '''

|}



{{Translation to follow}}

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

@@ Line 1: / Line 1: @@
-<!-- NAV -->
+{{OCIO_GCEA_Header}}
 <i>{{Translation to follow}}</i>
 <br>
@@ Line 74: / Line 55: @@
 ** Technical Debt
 ** Best in breed vs. suite?

@@ Line 20: / Line 20: @@
 <!-- NAV end -->
-<i>{{Translation to follow}}
+<i>{{Translation to follow}}</i>
 <br>
 <!-- Columns -->

@@ Line 27: / Line 27: @@
 | width="50%" style="color: blue;" |
 <!-- COLUMN 1 STARTS: --><span style="font-size: 1.5em;">[https://wiki.gccollab.ca/GC_Application_Enterprise_Architecture <b><<Application Architecture</b>]</span>
 <!-- COLUMN 1 ENDS: -->
 | width="50%" style="color: blue;" |
 <!-- COLUMN 2 STARTS: --><span style="font-size: 1.5em;">[https://wiki.gccollab.ca/GC_Security_and_Privacy_Enterprise_Architecture <b>Security Architecture>></b>]</span>
 <!-- COLUMN 2 ENDS: -->
@@ Line 59: / Line 57: @@
 ==Design for Performance, Availability, and Scalability==
 * Design for resiliency
 ** [https://principlesofchaos.org/?lang=ENcontent Chaos Engineering]
 * Ensure response times meet user needs, and critical services are highly available
 * Support zero-downtime deployments for planned and unplanned maintenance
 ** As your applications attract additional consumers, being able to introduce changes and patching without negotiating outages becomes more important
@@ Line 69: / Line 69: @@
 ** <nowiki>https://opentracing.io/</nowiki>
 * ''Establish architectures that supports new technology insertion with minimal disruption to existing programs and services''
 * ''Control Technical Diversity - design systems based on technologies and platforms already in use.''

@@ Line 20: / Line 20: @@
 <!-- NAV end -->
 <i>{{Translation to follow}}
 <br>
 <!-- Columns -->
@@ Line 29: / Line 28: @@
 | width="50%" style="color: blue;" |
-<!-- COLUMN 1 STARTS: -->
+<!-- COLUMN 1 STARTS: --><span style="font-size: 1.5em;">[https://wiki.gccollab.ca/GC_Application_Enterprise_Architecture <b><<Application Architecture</b>]</span>
 <!-- COLUMN 1 ENDS: -->
 | width="50%" style="color: blue;" |
-<!-- COLUMN 2 STARTS: -->
+<!-- COLUMN 2 STARTS: --><span style="font-size: 1.5em;">[https://wiki.gccollab.ca/GC_Security_and_Privacy_Enterprise_Architecture <b>Security Architecture>></b>]</span>
 <!-- COLUMN 2 ENDS: -->
@@ Line 46: / Line 43: @@
 ==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

@@ Line 36: / Line 36: @@
 <!-- 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: -->

← Older revision	Revision as of 18:43, 24 July 2020
(No difference)

← Older revision	Revision as of 14:49, 18 March 2019
(No difference)