1. Relevant Integration Patterns
1.1. Via Micro-Service integration layer
1.1.1. Pull: Active real-time integration from a system in the moment of data need.
1.1.1.1. use cases
1.1.1.1.1. Update of own fields already maintained in the system
1.1.1.1.2. Virtual extension with fields, not maintained in the system
1.1.1.2. assessment
1.1.1.2.1. Pro
1.1.1.2.2. Con
1.1.2. Push: Broadcast from one system to all relevant systems via publish and subscribe
1.1.2.1. use cases
1.1.2.1.1. Extension with fields, not maintained in the system. Fields are stored at target system
1.1.2.1.2. Update of own fields already maintained in the system
1.1.2.2. assessment
1.1.2.2.1. pro
1.1.2.2.2. con
1.2. Direct integration from system to system
1.2.1. pro
1.2.1.1. lesss complex in the beginning, as no middleware services need to be defined
1.2.2. Con
1.2.2.1. Difficult to maintain in an always changing system landscape
1.2.2.2. A single changing system might break the complete platform
2. Extended Customer Master Data Storage
2.1. No leading system
2.1.1. General Assessment
2.1.1.1. Pro
2.1.1.1.1. No system has more data than it needs
2.1.1.2. Con
2.1.1.2.1. No single system holding all customer data
2.1.1.2.2. Full customer record is only virtually available via real-time integration accross customer data holding systems
2.1.1.2.3. error-prone in terms of which system holds the correct data
2.1.1.2.4. always up to date documentation needed to prevent misunderstandings
2.1.1.2.5. It need to be defined, which system is allowed to update other: 1) Last Update is right, independent of system 2) Dedicated system per data field
2.2. Leading NEW System
2.2.1. General Assessment
2.2.1.1. Pro
2.2.1.1.1. Clear Responsibilities per system
2.2.1.1.2. Allows full decoupeling of all Omni-Channel platform solutions
2.2.1.2. Con
2.2.1.2.1. Additional cost for purchase and /or implementation
2.2.2. System Options
2.2.2.1. Buying Dedicated MDM System
2.2.2.1.1. Pro
2.2.2.1.2. Con
2.2.2.2. New Development of simplified full customer data store without dedublication
2.2.2.2.1. pro
2.2.2.2.2. con
2.3. Leading EXISTING System
2.3.1. General Assessment
2.3.1.1. Pro
2.3.1.1.1. Single system contains all relevant customer data
2.3.1.1.2. Clear responsibitlties
2.3.1.2. Con
2.3.1.2.1. One system contains more data than it needs
2.3.2. System Options
2.3.2.1. Commercetools
2.3.2.1.1. Pro
2.3.2.1.2. Con
2.3.2.2. PII
2.3.2.2.1. Information is missing...
2.3.2.3. LegoID
2.3.2.3.1. Pro
2.3.2.3.2. Con
2.3.2.4. CrowdTwist
2.3.2.4.1. Pro
2.3.2.4.2. Con
2.3.2.5. CRM
2.3.2.5.1. Pro
2.3.2.5.2. Con