Considerations and questions
- Scope
- The application interfaces for consideration
- To confirm the data being integrated
- Transport and Broking
- Is there an Enterprise Service Bus currently in use? Is this a standard that we should adopt
- Where does the demarcation between connected systems lie?
- Is Canonical Form being used?
- Is there a standard transport mechanism for messages between systems? Can we use the Azure Service Bus?
- Is there a standard used for systems to subscribe to messages of specific types?
- Are messages lightweight, and how should their payloads be informed?
- Resilience
- What status information should integrations return?
- Are there standards we should adopt for service availability and recovery?
- How should the connected systems recover from failure, regarding integrations?
- Are outages captured anywhere?
- Security
- To describe current good practices that we should adhere to.
- Confirm that we may use Azure Key Vault and Managed Identities as required.
- To confirm levels of encryption for data in transit.
- To confirm levels of encryption for data at rest.
- Operation
- For each set of data being moved, should this be synchronous/asynchronous?
- If synchronous, what would be the trigger?
- If asynchronous, what would be the frequency?
- Where should error messages be surfaced?
- Who will monitor and maintain the integrations?
- What telemetry should be captured and how?
- Will test systems for line-of-business applications be available?
