Het Microsoft Integratie Platform – Welk model past u het beste? (Steef Jan Wiggers at CONNECT17)
•
1 j'aime•283 vues
De wereld verandert, nieuwe technologieën komen op en uw integratieplatform moet daarop meebewegen. Welk platform kiest u, of houdt u in stand, om zowel on-premises als met de cloud te kunnen communiceren? Dankzij de komst van Microsoft Azure en haar nieuwe integratiediensten zijn er legio mogelijkheden. In deze sessie komen de diverse aspecten van on-premises (BizTalk/WCF) en het Azure platform aan bod. U krijgt een helder overzicht van de opties en hoort keuzes en overwegingen om de juiste keuze te komen.
Recommandé
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à Het Microsoft Integratie Platform – Welk model past u het beste? (Steef Jan Wiggers at CONNECT17)
Similaire à Het Microsoft Integratie Platform – Welk model past u het beste? (Steef Jan Wiggers at CONNECT17) (20)
Plus de Codit
Plus de Codit (16)
Dernier
Dernier (20)
Het Microsoft Integratie Platform – Welk model past u het beste? (Steef Jan Wiggers at CONNECT17)
- 1. #CONNECT17 Het Microsoft Integratie Platform: Welk model past u het beste? Steef-Jan Wiggers Azure Technology Consultant @SteefJan
- 2. Nice to meet you Steef-Jan Wiggers Azure Technology Consultant Codit Netherlands steefjan.wiggers@codit.eu +41 788 53 99 44 @SteefJan nl.linkedin.com/in/steefjan 8th year - Azure MVP
- 3. The thing we do
- 4. Agenda • Microsoft Enterprise Integratie • De Cloud (Azure) • Challenges • Codit aanpak
- 5. Integration
- 6. Application Landscape Yesterday Today Tomorrow IoT
- 7. Integration landscape Keep middleware close to the systems it integrates with. Decide with the company’s cloud strategy in mind!
- 8. Integration Landscape Yesterday Today Logic Apps API Mgmt Tomorrow Logic Apps API Mgmt Service Bus Azure Functions
- 9. On premise integration LOB Mature Roadmap Cloud Ready BizTalk Server • Out since 2000! • Running mission-critical productions workloads for years! Sentinet • Out since 2011! • Virtualizing API’s for years with minimal latency!On premise integration
- 10. On premise integration LOB Mature Roadmap Cloud Ready BizTalk Server • Huge commitment • Bringing more agility with Feature Packs! Sentinet • New HTML/JS user interface • API publication • More agile upgrade modelOn premise integration
- 11. On premise integration LOB Mature Roadmap Cloud Ready On premise integration Line of Business Integration • Host Integration Server • Many LOB / legacy connectors • SAP • Oracle • IBM • AS400 • MQSeries • …
- 12. On premise integration LOB Mature Roadmap Cloud Ready BizTalk Server • Service Bus Adapter • Logic Apps Adapter • Hosting in Azure IaaS Sentinet • Azure Service Bus Integration • More focus on REST, OAuth & OpenID Connect • Hosting in Azure IaaS On premise integration
- 13. Hybrid integration Organizations that adopt hybrid infrastructure will optimize costs and increase efficiency.
- 14. Hybrid integration By 2018, 20% of large organizations will use their hybrid integration platforms to integrate other platforms, to enable timely reaction to business moments. 75% of large organizations will establish a hybrid integration platform, by 2020.
- 15. Hybrid integration platform Connectivity Azure Hybrid integration Logic Apps API Mgmt Logic Apps • Modern & hybrid connectivity • 160+ Connectors • Secure & reusable connections API Management • REST + SOAP • Modern authentication • Network integration Velocity Network
- 16. Hybrid integration platform Connectivity Hybrid integration Logic Apps API Mgmt Network Integrated Azure Environment • Integration services • Messaging services • Storage & databases • Cognitive services • Reporting & analytics • Internet of Things • … Azure Velocity
- 17. Hybrid integration platform Connectivity Hybrid integration Logic Apps API Mgmt Network Logic Apps • Continuous releases • Two-paced integration • Customers influence roadmap API Management • Move fast, adapt fast • Quickly add new capabilities • Package and publish Azure Velocity
- 18. Hybrid integration platform Connectivity Hybrid integration Logic Apps API Mgmt VNET Integration • Point-to-Site VPN • Site-to-Site VPN • ExpressRoute Relays • Azure Relay Hybrid Connections • App Service Hybrid Connections • On-Premises Data Gateway Network Azure Velocity
- 19. Toolbox
- 21. Serverless By 2019 iPaaS will be the preferred option for new projects
- 22. Cloud integration Cloud integration Logic Apps API Mgmt Service Bus Serverless Pricing Migration ALM Serverless integration • No more server installation • No more server patching • Inherent high availability • Event based integration • Auto & instant scaling • … Azure Functions
- 23. Cloud integration Cloud integration Logic Apps API Mgmt Service Bus Serverless Pricing Migration ALM Logic Apps • Consumption based model • Pay per executed action • Monthly cost for enterprise features API Management • Monthly cost • Standard & premium tier Azure Functions
- 24. Cloud integration Cloud integration Logic Apps API Mgmt Service Bus Serverless Pricing Migration ALM Migration Path • SOAP to REST transformations • Integration Account • EDI / AS4 parsing • Flat File / XML parsing • Schemas & transforms • Enterprise connectors • Oracle, IBM, MQ, SAP… Azure Functions
- 25. Cloud integration Cloud integration Logic Apps API Mgmt Service Bus Serverless Pricing Migration ALM Azure Functions ALM • Native to cloud services • ALM governance is a must! • Continuous Integration • Continuous Delivery • ARM Templates • VSTS Release Management
- 26. Shift towards the Cloud
- 27. Different paths to shift towards cloud! On premise integration Cloud IaaS integration Hybrid integration Cloud serverless integration A natural evolution, not a revolution!
- 28. IaaS integration! What’s in it for you? On premise integration Why ? Strategy IaaS integration Reduce TCO Availability Security
- 29. • Order to cash On premise Integration EDI Order XML Order BizTalk Server XML Order Decartes EDI to XML XML Order EDI Invoice XML InoviceXML InoviceXML Inovice Dynamic AX
- 30. Hybrid integration! What’s in it for you? On premise integration Why ? Hybrid integration Logic Apps API Mgmt Flexibility Agility Innovation Future Proof
- 31. Hybride Integration Self-Service Portal API Management Outbound Inbound WebAPI WebAPI VIP Web Job Azure cache (REDIS) To Redis Storage (Azure) Web Job Dashboard Administrator/ Developer Portal Datastore Nuon (Windows) Service (Windows) Service Inbound Web Job Azure cache (REDIS) • Push customer data
- 32. Serverless integration! What’s in it for you? IaaS integration Why ? Serverless integration Logic Apps API Mgmt Service Bus Azure FunctionsLess devops Lower costs Instant scale Business value
- 33. Serverless Integration • Sync eLearning data with Dynamics CRM Online LMS365 API Custom API Service Bus Queue Dynamics CRM OnlineWebJobs Logic App
- 34. Demo
- 35. Routing Storage Account Events Storage blob Event Grid Logic App/FlowImage Cognitive Services Function Outlook email Notification Analysis WebHook Test Request Bin Computer Vision API Function Cognitive Services Analysis Face API
- 36. Challenges
- 37. Hybrid & cloud integration challenges NetworkingMonitoring Security
- 38. Networking: VNET Integration Site-to-Site VPN Express Route IPsec VPN <100 Mbps Active / Passive Cheap VLAN or via NSP < 10 Gbps Active / Active Expensive Technology Bandwidth Resilience Pricing
- 39. AppSvc Hybrid Connections Networking: relay solutions Azure Relay Hybrid Cnncts On Premises Data Gateway Firewall-friendly On premises API Web Socket Active / Active Firewall-friendly Client installation Application Level No High Availability Firewall-friendly Client installation TCP Tunnel (port) Active / Active
- 41. Monitoring Health monitoring Availability monitoring Performance monitoring Security monitoring SLA monitoring Auditing Usage monitoring Application logs Business monitoring Reporting …
- 42. Monitoring Health monitoring Availability monitoring Performance monitoring Security monitoring SLA monitoring Auditing Usage monitoring Application logs Business monitoring Reporting … Azure Monitor Log Analytics Application Insights Power BI Correlation Dash board Alerts
- 43. Codit Approach
- 44. The hybrid integration platform
- 45. The hybrid integration platform Monitoring App Insights OMS Power BI Integration Functions Logic Apps API Apps Messaging Service Bus Event Grid Connectivity Networking Azure Relay On premises Azure infrastructure Governance&security API Mgmt Active Directory KeyVault Administration Resource Manager Automation Portal
- 46. The hybrid integration platform Monitoring App Insights OMS Power BI Integration Functions Logic Apps API Apps Messaging Service Bus Event Grid Connectivity Networking Azure Relay On premises Azure infrastructure Governance&security API Mgmt Active Directory KeyVault Administration Resource Manager Automation Portal Codit Products! Proven integration patterns! One methodology! Guidelines& bestpractices 15 years of integration experience! Codit Managed Services! Jumpstart templates Agility & flexibility!
- 48. Integration is the backbone of your digital transformation. Now more than ever. 48 We want you to be fully connected. Apps. Data. Everything connected.
- 49. 49 Thank you! Keep in touch. Call or mail us. Ask us. Happy to help.
Notes de l'éditeur
- Introduce myself
- What Codit does. Integration in broad sense.
- Agenda of the talk
- Integration
- Before we dive into the evolution of integration, let’s have a look at the application landscape from yesterday’s, today’s and tomorrow’s organizations. Previously, all applications, which were mostly server products, were running in on premise data centers. If we face today’s reality, we see that the majority of the enterprises have a hybrid application landscape: the core applications are still running on premises, but they are already using some SaaS applications in the cloud such as Office365, SharePoint Online or Salesforce. Often, there are also trading partners which they interact with. When looking ahead at the future, cloud-based applications will take over our businesses and also Internet of Things will take a prominent place for certain organizations. Young start-ups have typically already a full cloud-based application landscape, whereas many traditional organizations carry a huge legacy with them. These organizations require a smooth digital transformation, without being disruptive.
- Explain Gartner’s quote
- Shift from where enterprises stand and move to the cloud. Yesterday, Today and Tomorrow spans decades.
- On premise integration spans at least a few decades from mainframe, client-server to internet. And BizTalk Server stands out since 2000.
- Roadmap of Microsoft is that they still support BizTalk the coming years to keep yesterday and today in tact. It bridges the gap between on premise and cloud.
- LOB Integration is the bread and butter of BizTalk and Sentinet.
- Cloud Ready means adapters for Logic Apps (On premise Gateway) and SB (Queues, Topics and Relay) or provide hosting for BizTalk capabilities in VM’s. Extensibility with on premise to cloud comes from Sentinet supporting Oauth and OpenID.
- Hybrid to save cost.
- Why investment in integration is necessary. Agility is key.
- Connectivity is main driver for hybrid. Sentinet, On premise datagateway or SB can act as a gateway to SaaS/Azure Services. API Management can act as host for (API) endpoints to support modern authentication such as Oauth and OpenID, aid in extending network boundaries.
- Azure Platform offers various services that can be leveraged
- Velocity means delivering solutions faster
- Networking
- Recap, our toolbox i.e. technology stack has grown. It’s span over a few decades of different paradigma Mainframe, Client-Server, Internet i.e. Cloud.
- One of the main characteristics of Microsoft’s cloud integration offering is the fact that it is serverless. This means you don’t need to take care of the underlying server infrastructure anymore. Serverless technology is high available by design and scales automatically and instantly, based on the number of received events. I provides an at-least-once execution model.
- Most PaaS services have a consumption based billing model. This means you pay per runtime execution. Within Logic Apps for example, you pay for every executed action. The enterprise integration features come with a fixed monthly cost. Consumption based billing is in many cases cheaper and if you combine this with the serverless setup, it often results in a reduced Total Cost of Ownership. API Management comes with a fixed monthly fee, based on the features you require.
- It should be clear that BizTalk integration flows cannot be migrated as-is to Logic Apps. However, thanks to the integration account, many artefacts can be uploaded to the cloud such as flat file schemas, edi schemas, transformation etc… Azure API Management also offers powerful SOAP to REST transformations, to modernize legacy services.
- A huge advantage of the modern cloud offering, is the fact that ALM was already considered right from the start. Nowadays, you need a solid ALM approach to continuously deliver new business value. The smooth integration of ARM templates and git endpoints within VSTS Release Management, ensures we have end-to-end traceability of the codebase throughout the different environments.
- It should be clear that shifting towards the cloud should be a natural evolution, not a revolution. It should be done without disrupting your running business. There are multiple ways to grow as an organization and integration platform gradually towards the cloud. Some organizations perform first a lift and shift towards the cloud and then gradually move towards serverless. Others keep their slowly moving core applications on premises, but add more agility by extending their integration platform through a hybrid setup.
- Why should you consider a lift and shift towards Azure Infrastructure as a Service? One reason could be to obtain better availability for your server infrastructure, which can span multiple Azure data centers. Improving your security could be another reason to move to Azure IaaS. Can you secure your data center better than Microsoft does? One example is the power of Azure Security Center, which identifies security threats, which gives you an investigation path when security incidents occur and allow you to take automated actions. In many scenarios, but don’t take it for granted, it allows you to reduce the total cost of ownership. As a last point, it’s important to mention that a lift-and-shift of the integration layer, is mostly part of the global strategy of an organization.
- Hybrid integration. Why should you consider expanding your on premises integration layer towards the cloud? An important reason is to be more flexible in your application landscape. Almost all modern SaaS applications offer an API layer, trough which you can easily connect your on premise systems, so you can choose a best of breed application. It also allows you to be more agile towards the business and release faster. We often see a two-paced integration: a rather slow moving core on premises and rapidly evolving cloud integration to support the business: e.g. launch quite fast a new sales / marketing campaign. Thanks to a hybrid setup, you can be more innovative than ever before. Don’t forget you have the complete Azure offering at your finger tips. Think about chatbots, sentiment analysis, speech-to-text service, face recognition, machine learning and predictive analysis and integration with Internet of Things. Be creative and innovative! Last but not least, a hybrid setup ensures you are set for the future and ready to tackle the upcoming challenges.
- What are to reasons to move to a completely serverless integration hub? By doing this, you can enormously reduce the efforts you put in operations: no more server patching, backups etc… Together with a consumption based billing model, this often results in lower costs, for sure for small and medium-sized organization. Serverless technology scales enormously, which avoids dimensioning servers the right way. Thanks to all these advantages, you can really focus on what matters, and that’s creating value with more innovative integrations than before!
- Governance: role based access control, separate subscriptions for prod <> non-prod, read-only access on production Firewall: dealing with public internet, so good configuration of network security groups Identity: service principals and managed identities in Active Directory Access Keys: solid ALM cycle and preferably stored in Azure KeyVault
- When we look at the Hybrid integration platform that Gartner defines, we see that it is more than the integration tools itself. It describes a complete platform that governs your full integration, with important aspects as security, application life cycle management, analytics, operations and very important a role-based user experience.
- This is reflected in the following diagram. On premises we have the known integration technologies running, in Azure we can leverage the standard compute and storage options. Networks enables smooth connectivity between on premises and the cloud. Messaging solutions like Service Bus and Event Grid allow great decoupling of application. At the center, we have Logic Apps that orchestrates all integrations that can be extended by Azure Functions and API Apps. From a security and governance perspective, there’s great integration with Azure API Management. Both users and services are given an identity by Azure AD, while we store passwords and keys encrypted in Azure Key Vault. To enable smooth administration and operations, we use VSTS Release Management to rollout the solutions throughout the DTAP street in a consistent manner. A role-based monitoring experienced is offered by App Insights for developers, OMS for operations and Power BI reports for business users.
- With Codit, we aim to be your trusted partner to setup your hybrid integration platform. We are on the edge of technology, collaborating with various Microsoft product groups and very active in the community. We have the knowledge and experience to turn Azure into a real hybrid integration platform, by glueing all the pieces together. Of course, we leverage our 15 years of integration experience. We use one methodology, which remains the same on premises or in the cloud. It’s based on proven integration patterns, of which publish/subscribe is probably the most important one. We foresee a lot of agility and flexibility, both in the solutions we deliver and in the way of collaborating with our customers. Our extended library with guidelines and best practices and jumpstart templates allow us to delivery quality in a fast way. We are backed by our Codit Products offering, that brings added value where we think Azure lacks some functionality and we have our Managed Services team which ensures a good follow-up of your solutions running in production.