Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Anatomy of an Enterprise Integration Architecture

547 views

Published on

Presentation delivered at INTEGRATE 2018 conference in London on 6th June

Published in: Technology
  • Be the first to comment

Anatomy of an Enterprise Integration Architecture

  1. 1. Dan Toomey Integration Architect and Microsoft AzureMVP Anatomy of an Enterprise Integration Architecture
  2. 2. Who am I? • Principal Consultant, Mexia • Microsoft Azure MVP • MCSE, MCT, MCPD, MCTS BizTalk & Azure • Pluralsight Author • www.mindovermessaging.com • @daniel2me
  3. 3. Who was I? • Principal Trombonist, Singapore Symphony Orchestra • USAF Band of Liberty • M.Mus, B.Mus - The Juilliard School • Founding member: – Paragon Ragtime Orchestra – Palisades Brass Quintet Photo by Brian Merritt
  4. 4. Acknowledgements Lee Simpson @LeeWSimpson Richard Seroter @RSeroter Mexia @TeamMexia
  5. 5. ComplexityofIntegration
  6. 6. ComplexityofIntegration
  7. 7. ComplexityofIntegration M E D S L O W F A S T
  8. 8. It’s about layers… … and the speed of change
  9. 9. How are we doing it? What are we doing it with? Where can we do it better?
  10. 10. About those layers…
  11. 11. Gartner’s Pace Layered Application Strategy
  12. 12. Gartner’s Pace Layers • New apps, ad hoc, new business reqs • Consumer-grade technologies Systems of Innovation • Unique processes / capabilities • Best of breed, SaaS, sometimes modules of a suite Systems of Differentiation • Core transaction processing • Critical master data Systems of Record
  13. 13. InnovationDifferentiationRecord Business Process Data / Information Change Control / Governance Business Engagement Planning Horizon
  14. 14. How are we integrating?
  15. 15. Systems of Innovation Systems of Differentiation Systems of Record E X T E R N A L S Y S T E M S
  16. 16. Systems of Innovation Systems of Differentiation Systems of Record Change Control API Design Testing Regime Rate of Change
  17. 17. What are we integrating with?
  18. 18. Systems of Innovation Systems of Differentiation Systems of Record Rate of Change
  19. 19. Technology Characteristics Technology Use When Considerations Product APIs • Product has granular APIs with a modern interface • APIs align with business needs • Vendor support is available + Tight integration with System of Record – Difficult or expensive to change or customize – May not suit business data model Web Service / REST APIs (IIS) • Exposing REST or SOAP interfaces • Implementing custom validation/security • Mapping to a canonical model + Inexpensive to host + Easy to consume – Development effort required API Management • Exposing APIs in the cloud • Implementing policy based security & access control • Leveraging caching/auditing/analytics/etc. + Customizable façade + Developer portal – Requires VNet Integration – No on-prem option – Expensive option if not using additional features Service Fabric • Aligning to a microservices architecture • Catering for multiple programming languages • Automated redundancy, load balancing, and no-downtime deployments are required + Can host anywhere + Supports containers – Development effort required BizTalk Server • OOTB adapters are available/suitable • Robust platform is required + BAM tracking available + Single platform integration – Expensive – Specialised dev skills required
  20. 20. Systems of Innovation Systems of Differentiation Systems of Record Rate of Change
  21. 21. Technology Characteristics Technology Use When Considerations Logic Apps • Business logic can be cloud hosted • Connecting with SaaS systems or other Azure services + Rapid development + 200+ built-in connectors! – No VNet support (until ISE becomes available) – No on-prem option (yet) Azure Functions • Need to run discrete pieces of stateless arbitrary code on demand • Integrating with other Azure services • Visual Studio development is preferred • Automated unit testing is a must + Good CI/CD support + VNet supported + Can run on-prem – Not as many connectors as Logic Apps Web/Mobile Apps • Cloud hosting is desired • Supporting multiple devices • Need a flexible programming model • Need exposure to external clients • Desire Blue/Green deployment slots + Good CI/CD support + Numerous deployment options + Azure Relay / VNet Integration supported – Not ideal in themselves for long running processes – Consider security layer for hybrid apps Service Fabric • Aligning to a microservices architecture • Catering for multiple programming languages • Automated redundancy, load balancing, and no-downtime deployments are required + Can host anywhere + Supports containers – Development effort required – Infrastructure investments (on-prem only) BizTalk Server • OOTB adapters are available/suitable • Robust platform is required • Wanting a reliable/durable workflow capability • Leveraging Business Rules Engine and/or BAM + Single platform for integration + Can be hosted on-prem or in Azure (IaaS) – Expensive – Specialised dev skills required
  22. 22. Systems of Innovation Systems of Differentiation Systems of Record Rate of Change
  23. 23. Technology Characteristics Technology Use When Considerations Microsoft Flow • Automating simple processes and tasks • Empowering business users to create their own integrations • Existing connectors are fit for purpose + Rapid development + Can be migrated easily to Logic Apps * Requires Office365 Power Apps • Developing in-house apps for devices • Leveraging built-in connectors + Easy integration with Flow / SharePoint / Dynamics 365 / Teams / etc. + Multi-platform * Requires Office365 Power BI • Need to quickly build custom charts and visuals • Integrate with multiple data sources * Relies on data sources Cognitive Services • Seeking advanced insights and analytic capabilities + Multiple services/APIs available (Vision, Knowledge, Language, Speech, Search) * Programming skills required Machine Learning • Seeking insights through predictive analytics * Data science skills required Bots • Seeking more human interaction with customers • Automating routine information retrieval or routing to appropriate support personnel * Programming skills required * Bots need to be trained well to function as expected
  24. 24. Systems of Innovation Systems of Differentiation Systems of Record Rate of Change
  25. 25. Technology Characteristics Technology Use When Considerations Event Grid • Building event-driven applications • Managing notifications • High scalability and throughput required • Handling events within Azure (or anywhere) + Resilient (retries up to 24 hours) + Push-push model + Easy to integrate * Small message size – No dead-lettering Event Hubs • Ingesting big data / streaming data • Replay / archiving is desired * Needs at least one downstream processor Relays • Need hybrid connectivity without firewall changes + Can use Hybrid Connection or WCF Relay On-Prem Data Gateway • Connecting Logic Apps to on-premises systems • Bridging SaaS applications to LOB systems + Good alternative to a VNet if using Logic Apps – Only supported by enterprise connectors Service Bus Queues • Decoupling sender / receiver processes • Each message should only be processed once • Data can flow through the cloud + Extremely resilient and full-featured – No on-prem option Service Bus Topics • Decoupling systems / processes via pub / sub • Supporting multiple subscribers to a message • Data can flow through the cloud + Extremely resilient and full-featured – No on-prem option BizTalk Server • Requiring robust pub/sub messaging • Leveraging BAM for tracking • Using OOTB adapters + Single platform for integration – Expensive – Specialised dev skills required
  26. 26. Where can we integrate better?
  27. 27. Consider how the application will be used
  28. 28. Make sure your System of Record layer is solid http://slideplayer.com/slide/3890847/
  29. 29. Limit customisation within the System of Record
  30. 30. Consider using canonical data models https://api-map.com/
  31. 31. Loosely couple inter-layer communications
  32. 32. Allow room for innovation
  33. 33. enquiries@mexia.com.au https://blog.mexia.com.au
  34. 34. Let’s connect! dan@mexia.com.au @daniel2me linkedin.com/in/danieltoomey mindovermessaging.com

×