139
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 (view source)
Revision as of 15:48, 5 March 2019
, 15:48, 5 March 2019linked API Standards
Line 106:
Line 106:
* Expose all functionality as services
* Expose all functionality as services
* Use microservices built around business capabilities. Scope each service to a single purpose
* Use microservices built around business capabilities. Scope each service to a single purpose
−* Run each IT service in its own process and have it communicate with other services through a well-defined interface, such as a HTTPS-based application programming interface (API)
+* Run each IT service in its own process and have it communicate with other services through a well-defined interface, such as a HTTPS-based [https://www.canada.ca/en/government/publicservice/modernizing/government-canada-standards-apis.html application programming interface (API)]
* Run applications in containers
* Run applications in containers
* Leverage the [[gccollab:groups/profile/1238235/engovernment-of-canada-digital-exchangefru00c9change-numu00e9rique-du-gouvernement-du-canada|GC Digital Exchange Platform]] for components such as the API Store, Messaging, and the GC Service Bus
* Leverage the [[gccollab:groups/profile/1238235/engovernment-of-canada-digital-exchangefru00c9change-numu00e9rique-du-gouvernement-du-canada|GC Digital Exchange Platform]] for components such as the API Store, Messaging, and the GC Service Bus
Line 141:
Line 141:
* Balance user and business needs with proportionate security measures
* Balance user and business needs with proportionate security measures
|}
|}
−<!-- FOOTER -->{| width="100%" cellpadding="10"
<!-- FOOTER -->{| width="100%" cellpadding="10"
