Dan Toomey Integration Architect and Microsoft Azure MVP

Dan Toomey Integration Architect and Microsoft Azure MVP Anatomy of an Enterprise Integration Architecture

Who am I? • • • Principal Consultant, Mexia Microsoft Azure MVP MCSE, MCT, MCPD, MCTS Biz. Talk & Azure Pluralsight Author www. mindovermessaging. com @daniel 2 me

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

Acknowledgements Lee Simpson @Lee. WSimpson Richard Seroter @RSeroter Mexia @Team. Mexia

Complexity of Integration

st Co of n at io gr te In Complexity of Integration

Complexity of Integration F A S T M E D S L O W

It’s about layers… … and the speed of change

How are we doing it? What are we doing it with? Where can we do it better?

About those layers…

Gartner’s Pace Layered Application Strategy

Gartner’s Pace Layers Systems of Innovation • New apps, ad hoc, new business reqs • Consumer-grade technologies Systems of Differentiation • Unique processes / capabilities • Best of breed, Saa. S, sometimes modules of a suite Systems of Record • Core transaction processing • Critical master data

Innovation Differentiation Record Business Process Data / Information Change Control / Governance Business Engagement Planning Horizon

How are we integrating?

Systems of Innovation Systems of Differentiation Systems of Record E X T E R N A L S Y S T E M S

Systems of Innovation Rate of Change API Design Change Control Systems of Differentiation Systems of Record Testing Regime

What are we integrating with?

Systems of Innovation Rate of Change Systems of Differentiation Systems of Record

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 Biz. Talk Server • • OOTB adapters are available/suitable Robust platform is required + BAM tracking available + Single platform integration – Expensive – Specialised dev skills required

Systems of Innovation Rate of Change Systems of Differentiation Systems of Record

Technology Characteristics Technology Use When Considerations Logic Apps • • Business logic can be cloud hosted Connecting with Saa. S 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) Biz. Talk 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 (Iaa. S) – Expensive – Specialised dev skills required

Systems of Innovation Rate of Change Systems of Differentiation Systems of Record

Technology Characteristics Technology Microsoft Flow Use When Considerations + Rapid development + Can be migrated easily to Logic Apps * Requires Office 365 • Automating simple processes and tasks Empowering business users to create their own integrations Existing connectors are fit for purpose Power Apps • • Developing in-house apps for devices Leveraging built-in connectors + Easy integration with Flow / Share. Point / Dynamics 365 / Teams / etc. + Multi-platform * Requires Office 365 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 • •

Systems of Innovation Rate of Change Systems of Differentiation Systems of Record

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 Saa. S 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 Biz. Talk Server • • • Requiring robust pub/sub messaging Leveraging BAM for tracking Using OOTB adapters + Single platform for integration – Expensive – Specialised dev skills required

Where can we integrate better?

Consider how the application will be used

Make sure your System of Record layer is solid http: //slideplayer. com/slide/3890847/

Limit customisation within the System of Record

Consider using canonical data models https: //api-map. com/

Loosely couple inter-layer communications

Allow room for innovation

enquiries@mexia. com. au https: //blog. mexia. com. au

Let’s connect! dan@mexia. com. au @daniel 2 me mindovermessaging. com linkedin. com/in/danieltoomey