Downloaded 20 times
Uploaded byCallon Campbell
Serverless integrations using Azure Logic Apps (intro)
The document introduces Azure Logic Apps, which facilitate serverless workflows to integrate disparate systems easily. It outlines key components such as connectors, triggers, and actions, emphasizing the platform's scalability and user-friendly tools. Additionally, it provides resources for further exploration and highlights the benefits of using Logic Apps in various integration scenarios.
Serverless integrations using Azure Logic Apps (intro)
- 1. Serverless integrations using AzureLogic Apps Callon Campbell
- 2. Microsoft Azure About me CallonCampbell Systems Architect / Developer. With over 19 years of experience developing desktop, mobile and web enterprise applications using Microsoft .NET Framework, SQL Server and Azure technologies. Co-founder of ReflectSoftware Inc and one the principle developers of ReflectInsight, a real-time .NET logging/analytics framework and Live/Log Viewer. 2 Email: CallonCampbell@Outlook.com Twitter: @Flying_Maverick, @DevelopAzure Blog: http://TheFlyingMaverick.com LinkedIn: LinkedIn.com/in/calloncampbell Website: http://ReflectInsight.com
- 3. Microsoft Azure Agenda •Introduction toAzure Logic Apps •Sample scenarios •Demo •Wrap up 3
- 4.
- 5.
- 6. Microsoft Azure What areLogic Apps? • Serverless workflows that allow developers to easily integrate data with their apps instead of writing complex glue code between disparate systems • Fully managed iPaaS (integration Platform as a Service) • Orchestrate and connect the serverless functions and APIs between your systems, applications and services
- 7. Microsoft Azure Logic Appsare Serverless •Abstraction of servers •Event-driven •Instant scale •Consumption billing 7
- 8. Microsoft Azure Why LogicApps? •Implement workflows seamlessly •Use simple, user-friendly and intuitive tools •Connect systems across on-premise and cloud •Jumpstart with pre-defined templates •Create scalable integrations without coding •Extend default capability with Azure Functions •Reach out easily to other Azure services 8
- 9. Microsoft Azure Components ofLogic Apps Logic Apps consist of four components: • Connectors • Triggers • Conditions • Actions 9
- 10. Microsoft Azure Connectors • Connectorsare an integral part when creating logic apps • Out-of-the-box connectors reduce integration challenges and enable you to connect apps, data and devices anywhere • Currently there are over 140 connectors 10
- 11. Microsoft Azure Triggers • Triggersallow a Logic App to “run” • Recurring schedule – every “x” sec/min/hour • Poll an API for a response • A 200 response means “run” while a 202 response means “wait” • Request webhook • Every workflow has an endpoint you can POST to using a SAS URL • Webhook subscription • Subscribe to a web service webhook • On Demand • Manual invocation from the “Run Now” button in the portal 12
- 12. Microsoft Azure Actions •Invoke services: •Managed Connectors • App Service API Apps • APIs through API Mgnt • Azure Functions • Http + Swagger • Direct Http endpoints • Nested Workflows 13 •Request handling • Response •Message composition •Flow control •Conditions and loops •Built in retry policy • Default is 4x/20sec
- 13.
- 14.
- 15. Microsoft Azure Quickly tapinto the power of the cloud Fire workflows on events from other services 16
- 16. Microsoft Azure Orchestrate anything • Runmission-critical, complex integrations scenarios with ease • Easily connect custom on-premises applications to the cloud • Connect on-premises, hybrid and cloud applications • Position for future with API centric connectivity 17
- 17. Demo: Creating a newLogic App
- 18. Microsoft Azure Management andMonitoring Azure portal provides debugging and history: • Trigger history shows polling results • Run history shows details for each logic app run • Run statistics • Action execution log • All of the inputs to the action • All of the outputs from the action • Status and errors • Also available by API and SDK 20
- 19.
- 20. Microsoft Azure Summary •Workflow enginebuilt for the cloud - cloud scale, massive compute and high availability are built in •iPaaS & Serverless •Easy creation of integration workflows •Huge amount of connectors (+140) •Hybrid integration •Better together with BizTalk Server 22
- 21. Microsoft Azure What’s next? •TryLogic Apps for free: http://aka.ms/logicapps-try •Blog: https://blogs.msdn.microsoft.com/logicapps/ •Twitter: @LogicAppsIO •Learn more at Microsoft Virtual Academy and Channel 9 23
- 22.
- 23. Microsoft Azure References • https://azure.microsoft.com/en-ca/services/logic-apps/ •https://azure.microsoft.com/en-ca/pricing/details/logic-apps/ • https://portal.azure.com/ • https://serverless.com/blog/event-driven-influencers-microsoft- azure/ • https://docs.microsoft.com/en-ca/azure/logic-apps/logic-apps- deploy-from-vs/ 25
Editor's Notes
- #5 Wouldn’t it be nice if you could easily connect all the applications and services your business relies on…
- #6 Well now you can with Azure Logic Apps. Azure Logic Apps are built around the idea of events, triggers and workflows. When you think about building microservices, there are a lot of moving parts to manage. Azure Logic Apps lets you stitch them all together much more easily, and provides you with a central place to build and manage all of your event-driven services.
- #8 Servers are abstracted away (no need to manage, monitor, upgrade or patch). Event driven – Trigger apps based on any event. Instant scale – Cloud scale, massive compute, high availability are built in. Consumption billing – Only pay for what you use.
- #9 Logic Apps bring speed and scalability into the enterprise integration space. Logic Apps provide easy to use design tools. You can easily connect APIs from almost any system. Start with pre-defined templates or start from scratch. Extensibility is baked-in (call Azure Functions) Real integration horsepower – connect with other Azure Services and take advantage of cloud scale.
- #14 Can have a custom retry policy
- #15 Response – For every action that comes in you can have a response that is sent back to that request. For Each – Iterate over a collection of items on an action. Split On – Split an array so a new workflow runs for each item in that array in parallel. Do Until – Have that action run until a certain condition is met. Conditions – A condition determines whether an action should run.
- #17 A classic example - businesses can monitor Tweets and Facebook posts collecting data and sending to cognitive services where you can perform sentiment analysis. In the case where negative data is received, a ticket can be logged in JIRA or other systems so an employee can take action and follow up with the client.
- #19 Use a Logic App to monitor an FTP site (polling trigger). File is picked up and can be stored to Azure Blog Storage for future reference. The file is then passes to an Azure Function or API App to parse the data into JSON. The Logic App can then iterate over each record and add to a queue. Then we have another Logic App that will pickup the data from the queue, perform some task and then save into a database. All without any code.
- #20 https://portal.azure.com/ When I get an urgent email, I want to track that email and create a corresponding item in Wunderlist. Trigger based on priority email Use an Outlook connector Tokens are provided automatically based on the action and connector Use a Wunderlist connector
- #22 Logic Apps aren’t limited to the Azure Portal….you can use Logic Apps tools for Visual Studio. Here you have a hosted designer, access to source control and CI/CD and much, much more.