system-type-enterprise-integration Skill

Source

• Creator: microsoft
• Repository: microsoft/amplifier-bundle-systems-design
• Skill file: skills/system-type-enterprise-integration/SKILL.md

What it does

Domain patterns for enterprise integration — legacy modernization, strangler fig, anti-corruption layers, API gateways, canonical data models, event-carried state transfer, and failure modes. Use when designing or evaluating integration between existing enterprise systems, legacy modernization, or multi-system orchestr

Skill instructions

System Type: Enterprise Integration Patterns, failure modes, and anti-patterns for connecting, modernizing, and orchestrating enterprise systems. --- 1. Integration Patterns Enterprise integration is the art of making systems talk to each other when they were never designed to. Every pattern trades coupling for something — throughput, consistency, simplicity, or debuggability. The right choice depends on what you can afford to lose. The Topology Spectrum | Topology | Description | Coupling | Failure domain | Debuggability | When it works | |---|---|---|---|---|---| | Point-to-point | Direct connections between each pair of systems. N systems → N×(N-1)/2 connections. | Tightest — every system knows every other system's interface | Localized but unpredictable — one system's outage cascades differently depending on who depends on it | Easy when there are 3 systems, impossible at 15 | Small number of integrations (<5 systems), throwaway prototypes, or when two systems genuinely have a 1:1