Line 62: |
Line 62: |
| Application architecture practices must evolve significantly for the successful implementation of the GC Enterprise Ecosystem Target Architecture. Transitioning from legacy systems based on monolithic architectures to architectures that oriented around business services and based on re-useable components implementing business capabilities, is a major shift. Interoperability becomes a key element, and the number of stakeholders that must be considered increases. | | Application architecture practices must evolve significantly for the successful implementation of the GC Enterprise Ecosystem Target Architecture. Transitioning from legacy systems based on monolithic architectures to architectures that oriented around business services and based on re-useable components implementing business capabilities, is a major shift. Interoperability becomes a key element, and the number of stakeholders that must be considered increases. |
| | | |
− | === Use Open Source Solutions hosted in Public Cloud[edit | edit source] === | + | === Use Open Source Solutions hosted in Public Cloud === |
| * 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 |
| * Register Open Source software to the Open Resource Exchange | | * Register Open Source software to the Open Resource Exchange |
| | | |
− | === Use Software as a Service (SaaS) hosted in Public Cloud[edit | edit source] === | + | === Use Software as a Service (SaaS) hosted in Public Cloud === |
| * Choose SaaS that best fit for purpose based on alignment with SaaS capabilities | | * Choose SaaS that best fit for purpose based on alignment with SaaS capabilities |
| * Choose a SaaS solution that is extendable | | * Choose a SaaS solution that is extendable |
| * Configure SaaS and if customization is necessary extend as Open Source modules | | * Configure SaaS and if customization is necessary extend as Open Source modules |
| | | |
− | === Design for Interoperability[edit | edit source] === | + | === Design for Interoperability === |
| * Design systems as highly modular and loosely coupled services | | * Design systems as highly modular and loosely coupled services |
| * Expose services, including existing ones, through APIs | | * Expose services, including existing ones, through APIs |