Cloud integration: what's in it for you? (Toon Vanhoutte & Massimo Crippa at CONNECT17)
•
1 like•348 views
This session focuses on the great opportunities that cloud integration brings to your business. Common challenges and pitfalls for hybrid messaging-based and API-based integration are discussed. Next to that, Codit's added-value approach to hybrid integration is presented, which combines a solid foundation of 15 years integration experience with an innovative and rapidly moving Azure cloud platform.
Recommended
Recommended
More Related Content
What's hot
What's hot (20)
Viewers also liked
Viewers also liked (20)
Similar to Cloud integration: what's in it for you? (Toon Vanhoutte & Massimo Crippa at CONNECT17)
Similar to Cloud integration: what's in it for you? (Toon Vanhoutte & Massimo Crippa at CONNECT17) (20)
More from Codit
More from Codit (20)
Recently uploaded
Recently uploaded (20)
Cloud integration: what's in it for you? (Toon Vanhoutte & Massimo Crippa at CONNECT17)
- 1. #CONNECT17 Cloud integration: what's in it for you? Toon Vanhoutte & Massimo Crippa Lead Architect & APIM Domain Lead @ToonVanhoutte & @mas_que_crippa
- 2. The thing we do
- 3. Agenda • Integration scenarios • Shift towards cloud • Challenges • Codit Approach • Q&A
- 5. Application Landscape Yesterday Today Tomorrow IoT
- 6. 6 Integration landscape Keep middleware close to the systems it integrates with. Decide with the company’s cloud strategy in mind!
- 7. Integration Landscape Yesterday Today Logic Apps API Mgmt Tomorrow Logic Apps API Mgmt Service Bus Azure Functions
- 8. 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
- 9. 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
- 10. 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 • …
- 11. 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
- 12. 12 Hybrid integration Organizations that adopt hybrid infrastructure will optimize costs and increase efficiency.
- 13. 13 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.
- 14. 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 • Connect to APIs built and running on any technology Velocity Network
- 15. 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
- 16. 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
- 17. 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
- 18. 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
- 19. 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
- 20. Cloud integration Cloud integration Logic Apps API Mgmt Service Bus Serverless Pricing Migration ALM Migration Path • SOAP to REST transformations • Integration Account • EDI / AS2 parsing • Flat File / XML parsing • Schemas & transforms • Enterprise connectors • Oracle, IBM, MQ, SAP… Azure Functions
- 21. 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 • Git Endpoints • VSTS Release Management
- 23. Different paths to shift towards cloud! On premise integration Cloud IaaS integration Hybrid integration Cloud serverless integration A natural evolution, not a revolution!
- 24. IaaS integration! What’s in it for you? On premise integration Why ? Strategy IaaS integration Lower Costs Availability Security
- 25. Hybrid integration! What’s in it for you? On premise integration Why ? Hybrid integration Logic Apps API Mgmt Flexibility Agility Innovation Future Proof
- 26. Serverless integration! What’s in it for you? IaaS integration Why ? Serverless integration Logic Apps API Mgmt Service Bus Azure FunctionsLess devops Reduce TCO Instant scale Business value
- 27. Demo time! Self-service B2C integration Activate via the Teamleader marketplace Invoices are automatically synced with KBC ComFinTouch Invoice status updated when invoice is paid TeamLeader 1. Webhook 2. Get invoice 3. Get company (4. Create debtor) 5. Add invoice Invoice created
- 28. Challenges
- 29. Challenges on the road to transformation INITIATION EXECUTION GOVERNANCE • Skepticism • Regulations • Business case • Skills • Resistance to change • Vision • Coordination
- 30. Hybrid & cloud integration challenges NetworkingMonitoring Security
- 31. 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
- 32. 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
- 34. Monitoring Health monitoring Availability monitoring Performance monitoring Security monitoring SLA monitoring Auditing Usage monitoring Application logs Business monitoring Reporting …
- 35. 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
- 36. Codit approach
- 37. The hybrid integration platform
- 38. 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
- 39. 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 Software! Proven integration patterns! One methodology! Guidelines& bestpractices 15 years of integration experience! Codit Managed Services! Jumpstart templates Agility & flexibility!
- 40. Thank you! Keep in touch. Call or mail us. Ask us. Happy to help.
Editor's Notes
- Here what we do. Connecting people and technology.
- Massimo:
- Massimo: 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 most of the enterprises have a hybrid application landscape: the core applications are still running on premises, but they have moved or they are starting to move some of their applications and processes to the cloud – especially in combination with SaaS applications like Salesforce or Office 365. All of those modern software solutions are powered by APIs. The API are the building blocks of your Digital Transformation and the digital glue that links data, applications and systems. Non only cloud applications but also interactions with business partners. While it is possible to build a custom integration for each partner, the best approach is to provide to those partners access to data and functionalities via an API. 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. Start-ups typically already have a full cloud-based application landscape, and cloud only architectures so they already are cloud only.. on the other hand, traditional organizations carry a huge legacy with them. These organizations require a smooth digital transformation, without a big bang approach.
- Massimo: Let’s have a look at the integration landscape keeping in mind that is a best practice to keep the middleware close to the systems that integrates for example for performance and availability reasons. And decide what is the missing integration features and evolve strategically according to the business and IT priorities.
- Massimo: Here how we can map the integration landscape Yesterday, today and tomorrow. Many organizations, especially medium and large, already have in place some ESB, ETL, B2B gateway software and API management platforms. Today, the directors of integration they are busy figuring out how to extend their integration infrastructure to support new needs (like cloud SaaS integration) and what are the missing functionalities they need to add to to target their hybrid platform (they need) And tomorrow the proliferation of cloud applications will result in the need of a cloud platform to integrate messages, react to events and enable business interactions.
- Massimo: This is how we do integration for years. We are using mature Microsoft technology to solve business needs. BizTalk is running mission critical workloads for years without losing a single message. Sentinet API Management is helping our customer in their API strategy adding features like design time and runtime governance and security.
- Massimo: They both have a clear road map mainly focused in adding agility and supporting latest technologies.
- Massimo: When your core business processes are on premises products like BizTalk still bring a huge added value in integrating LOB systems like HIS or SAP
- Massimo: And finally, the products in our portfolio they are both cloud ready supporting different hosting models and supporting, of the box, technologies like service bus which is the core component for scalable and distributed solutions.
- Massimo: Now, What are the organization needs of today? … Gartner told us that the organizations that adopt hybrid infrastructure will optimize cost (a lower TCO) and optimize efficiency (thanks to the access to a multitude of cloud software and services).
- Massimo: They also told us 75% of large enterprise will use hybrid platform to enable timely reactions to business moments. This means having a flexible platform to move fast, adapt fast to get the business opportunities. The proliferation and growing importance of decentralized integration tasks are forcing IT-Managers to rethink their approaches, organizational models and technology platforms.
- Massimo: Today we see more and more integration platforms evolving to the hybrid model. The HIP combines your on premises integration platform with multiple Innovative platforms (iPaaS, iSaaS and API management). We said that for on premise it’s very important to have a comprehensive set of LOB Adapter, same story here in the cloud – connectivity is fundamental. Being able to support modern standards, having out of the box connectors with the cloud solutions, having a a model that enable and promote the reuse of connections
- Massimo: Here on the top we put two main components of a Hybrid integration platform but this is not the full picture of your HIP because choosing Azure you can get lot more benefits from the Microsoft cloud like messaging services, storage, reporting and so on.
- Massimo: This type of platform gives you the possibility to speed up your go to market. You can achieve a multiple pace integration where on prem you have stable core components and on the cloud solutions that move fast and adapt fast according to the business needs. Velocity and agility are in the DNA of the components of a HIP
- Massimo: And finally a very important point, the network integration. Network a key aspect in choosing one platform rather the other. Microsoft Azure has the more complete networking offer because foresee the need of multiple connectivity modes early on compared to competitors so they started to buiild their cloud with the goal to enable the hybrid integration as first scenario.
- Toon: 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.
- Toon: 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.
- Toon: 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.
- Toon: 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.
- Toon: Let have a look why and how you can move as a traditional organization more and more towards the cloud.
- Toon: 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.
- Toon: 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.
- Toon: 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.
- Toon: 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!
- Toon: One great example of the agility that hybrid integration brings, is the following case at KBC Commercial Finance. I was asked to try to migrate a BizTalk flow to Logic Apps, as an R&D project. Suddenly, Danny came to me and shared an idea to have integration with Teamleader, an online tool for project management, CRM and invoicing. Three hours later, we had already a demo prepared. We dropped the R&D project an focused immediately on the following integration. KBC Commercial Finance want to be in the Teamleader market place, where you can enable the integration as an end-user by just allowing access to both your Teamleader and KBC ComFinTouch account. When an invoice is created in Teamleader, a Logic App gets fired via a registered webhook. The Logic App retrieves the Invoice and Company details from Teamleader and creates the invoice in ComFinTouch. Let’s have a look at the demo. As we are not live yet with this integration, I’ll show you the acceptance environment. This gives me also an excuse if the demo fails.
- Toon: So Massimo, I can imagine that the cloud also brings some complexity and extra challenges. Can you elaborate a bit more on that?
- Massimo: Digital transformation is not only a technology challenge, but also a management and people challenge. Challenges occur in all three elements of the transformation process: There will be skepticism (why should I move data or part of my business process somewhere else?), Maybe there is not ( yet a) clear business case…What is the value that this solution is bringing? Or you might experience doubts about whether or not your company has the right digital skills? Do you have to invest on the missing digital skills? And then challenges in the governance, like not a clear vision, or coordination issues, these can block or slow down the transformation process.
- Massimo: And then technical challenges that the cloud integration may bring. Networking, Security and Monitoring.
- Massimo: There are different Network integration for different company sizes You can choose for a VPN integration Rather than a dedicated connection via express route They are using different technology. S2S uses IPSec VPN so it’s interoperable with most VPN devices Express route can leverage a direct VLAN integration One is way more expensive that the other on the other hand it also depends on the capacity you need we can see that one have a bandwidth up to 100 Mbps, the other up to 10 Gbps. This is an enterprise level choice, so you set it up once and all the components/ application can get the benefits, while on the other hand….
- Massimo: Another approach is leveraging the RELAY solution and take pick up one or the other depending on the application/integration. Hybrid integration are easier with Azure because Microsoft foreseen the need of different connectivity models early on compared to other competitors and now have the best offer in this space.
- Massimo: 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. DdoS, sql injetions. Recently microsoft extented his offer with a new DdoS protection service that offer additional protection at L3/L4 (network and transport )lever L7 level (application level) Identity: service principals and managed identities in Active Directory Access Keys: solid ALM cycle and preferably stored in Azure KeyVault
- Massimo:
- Massimo: So the road of the digital transformation is not gold paved, there are many challenges, transformation cannot happen overnight … but the message here is that the transformation can happen in every organization, of any size, in any sector or country.
- Toon:
- Toon: 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.
- Toon: 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 KeyVault. 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.
- Toon: 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.