2,055
edits
Changes
Jump to navigation
Jump to search
mLine 27:
Line 27: − − Line 59:
Line 57: + + Line 69:
Line 69: + + + +
GC Enterprise Architecture/Standards/Technology Architecture (view source)
Revision as of 10:19, 27 August 2019
, 10:19, 27 August 2019Spike in more placeholders
| width="50%" style="color: blue;" |
| 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 STARTS: --><span style="font-size: 1.5em;">[https://wiki.gccollab.ca/GC_Application_Enterprise_Architecture <b><<Application Architecture</b>]</span>
<!-- COLUMN 1 ENDS: -->
<!-- COLUMN 1 ENDS: -->
| width="50%" style="color: blue;" |
| 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 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: -->
<!-- COLUMN 2 ENDS: -->
==Design for Performance, Availability, and Scalability==
==Design for Performance, Availability, and Scalability==
* Design for resiliency
* Design for resiliency
** [https://principlesofchaos.org/?lang=ENcontent Chaos Engineering]
** [https://principlesofchaos.org/?lang=ENcontent Chaos Engineering]
* Ensure response times meet user needs, and critical services are highly available
* Ensure response times meet user needs, and critical services are highly available
** <nowiki>https://royal.pingdom.com/page-load-time-really-affect-bounce-rate/</nowiki>
* Support zero-downtime deployments for planned and unplanned maintenance
* 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
** As your applications attract additional consumers, being able to introduce changes and patching without negotiating outages becomes more important
** <nowiki>https://opentracing.io/</nowiki>
** <nowiki>https://opentracing.io/</nowiki>
* ''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''
** API Gateways???
** General SOA???
* ''Control Technical Diversity - design systems based on technologies and platforms already in use.''
* ''Control Technical Diversity - design systems based on technologies and platforms already in use.''
** Technical Debt
** Best in breed vs. suite?
