139
edits
Changes
Jump to navigation
Jump to search
Line 266:
Line 266: − + + + +
GC Enterprise Architecture/Enterprise Solutions (view source)
Revision as of 09:14, 24 August 2020
, 09:14, 24 August 2020→DRAFT: Patterns and Practices regarding Enterprise Solutions/Shared Services: Spectrum of Options
|[[File:Decentralized Model Icon.png|alt=Decentralized Model Icon|thumb|100x100px|Decentralized Model Icon]]
|[[File:Decentralized Model Icon.png|alt=Decentralized Model Icon|thumb|100x100px|Decentralized Model Icon]]
|-
|-
|'''Federated Model.''' This stand alone, or decentralized model allows departments to implement their own stack components, influenced by standards, using APIs via interoperability standards. Governance manages exemptions from the Standard; however, a decentralized enterprise with multiple service delivery methods and business units may be successful in finding justifications for significant deviations for standards
|'''Federated Model.''' This stand alone, or decentralized model allows departments to implement their own stack components, influenced by standards, using APIs via interoperability standards. Governance manages exemptions from the Standard; however, a decentralized enterprise with multiple service delivery methods and business units may be successful in finding justifications for significant deviations for standards.
'''Pros''': Enables reactive solutions to address business processes not shared across departments. Limited risk of vendor lock in.
'''Cons''': Limits reuse across departments. Talent supporting technology components in the federated model have fewer opportunities to build skill sets useful across the Enterprise.
|[[File:Federated Model Icon.png|alt=Federated Model Icon|thumb|100x100px|Federated Model Icon]]
|[[File:Federated Model Icon.png|alt=Federated Model Icon|thumb|100x100px|Federated Model Icon]]
|}
|}
