Het Microsoft Integratie Platform – Welk model past u het beste? (Steef Jan Wiggers at CONNECT17)

Editor's Notes

• #3: Introduce myself
• #4: What Codit does. Integration in broad sense.
• #5: Agenda of the talk
• #6: Integration
• #7: 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.
• #8: Explain Gartner’s quote
• #9: Shift from where enterprises stand and move to the cloud. Yesterday, Today and Tomorrow spans decades.
• #10: On premise integration spans at least a few decades from mainframe, client-server to internet. And BizTalk Server stands out since 2000.
• #11: 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.
• #12: LOB Integration is the bread and butter of BizTalk and Sentinet.
• #13: 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.
• #14: Hybrid to save cost.
• #15: Why investment in integration is necessary. Agility is key.
• #16: 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.
• #17: Azure Platform offers various services that can be leveraged
• #18: Velocity means delivering solutions faster
• #19: Networking
• #20: 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.
• #23: 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.
• #24: 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.
• #25: 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.
• #26: 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.
• #28: 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.
• #29: 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.
• #31: 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.
• #33: 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!
• #41: 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
• #45: 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.
• #46: 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.
• #47: 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.