Line 72: |
Line 72: |
| <span style="font-size: 1.5em;">[[GC_Application_Enterprise_Architecture | 3. Application Architecture]]</span> <br><br> | | <span style="font-size: 1.5em;">[[GC_Application_Enterprise_Architecture | 3. Application Architecture]]</span> <br><br> |
| | | |
− | <b><I><u>Use Open Source Solutions hosted in the Cloud</b> | + | <b><I><u>Use Open Source Solutions hosted in Public Cloud</b> |
| * Select existing solutions that can be reused over custom built | | * Select existing solutions that can be reused over custom built |
| * Contribute all improvements back to the communities | | * Contribute all improvements back to the communities |
Line 78: |
Line 78: |
| <br> | | <br> |
| | | |
− | <b>Use SaaS hosted in the Cloud</b> | + | <b>Use Software as a Service (SaaS) hosted in Public Cloud</b> |
− | * Choose SaaS that are extendable | + | * Choose SaaS that best fit for purpose based on alignment with SaaS capabilities |
− | * Align with SaaS capabilities; extend as Open Source modules | + | * Choose a SaaS solution that is extendable |
− | * Configuration over customization
| + | * Configure SaaS and if customization is necessary extend as Open Source modules |
| <br> | | <br> |
| | | |
| <b>Design for [https://www.gcpedia.gc.ca/wiki/En/GCinterop Interoperability]</b> | | <b>Design for [https://www.gcpedia.gc.ca/wiki/En/GCinterop Interoperability]</b> |
− | * Design systems to be highly modular, loosely coupled and aligned to Business Capability Model 2.0 | + | * Design systems as highly modular and loosely coupled services |
− | * Use micro services scoped to a single purpose and API-led connectivity
| + | * Expose services through APIs |
− | * Expose functionality as services, make services available through APIs and make the APIs discoverable | + | * Make the APIs discoverable to the appropriate stakeholders |
| <br> | | <br> |
| | | |