Choosing Integration Technology (1)

Op de BizTalk Summit 2014 in London heeft Richard Seroter een interessante presentatie over het selecteren van de juiste integratie technologie gehouden: “When to use what: A look at choosing integration technology”. In deze eerste blogpost geef ik de verschillende selectiecriteria weer. Seroter onderscheidt hierbij de volgende categorieën:
  • Organization strategy
  • Design
  • Development
  • Operations
Uitwerking: Organization strategy o   Long-term solution fit (levensduur: lange termijn of alleen prototype) o   Vendor support available (denk aan open source) o   Use existing software investments o   Budget impact o   Build vs Buy philosophy o   Risk tolerance (new technology OK?) o   Speed to market o   Open Source Components o   Commodity skill set (volwassen technologie?) Design o   Data volumes o   Guaranteed delivery o   Data sources en data destinationations (vb SSIS voor DB to DB) o   Latency o   Authentication/authorization (sophisticated) o   Failure handling o   Endpoint location, reliability * o   Constraints * o Circuit breakers. Stel: 9 calls, de derde faalt, wat nu? * Development o   Developer availability o   Learning curve o   Developer setup o   IDE and tool integration o   Support system (vb. knowledge base articles, discussion groups) o   Automated build support o   Deploy to cloud * o   Webbased development tools * o   Continuous Integration / Delivery * Operations o   Event logging o   Performance tuning o   Burst and failure handling o   Backup/Restore o   Scriptability (Powershell) o   Immutable servers (build a server in less than an hour) * o   Rapid release / roll-back * o   Distributed deployments (1 app, 9 datacenters, possible?) * Sterretje(*) – Attributen relevant voor de cloud