Azure Serverless with Functions, Logic Apps, and Event Grid Notes: • If you experience audio issues during the webinar, you can dial in through telephone details provided to you in your registration confirmation email. • Please feel free to post questions in the questions dialog & we will try to answer as many as we can at the end. • Recording of this session will be shared in next 24-48 hours. • You can also write to us at marketing@winwire.com for any clarifications or information.
Session Speaker Viplove Sharma Technical Architect WinWire Technologies
3. Logic Apps 4. Event Grid 2. Azure Functions 5. Demo 1. Serverless Computing 6. Q & A Agenda
Evolution of Cloud Computing Data Centres Infrastructure as a Service (IaaS) Platform as a Service (PaaS) Container as a Service (CaaS) Serverless (FaaS) Software as a Service (SaaS)
Serverless Computing An abstraction of servers, infrastructure and operating systems Dynamic allocation of resources, driven by events/triggers in near real-time Pricing based on actual consumption of resources Servers still required!
Azure Serverless Fully managed services ranging from compute, storage, database, orchestration, monitoring, analytics, and intelligence to help construct serverless applications for any kind of scenario Azure Functions Azure Storage Azure Cosmos DB Azure Active Directory Logic Apps Service Bus Event Grid API Management Event Hubs Azure Bot Service Cognitive Services Azure Stream Analytics Application Insights
Azure Functions
Azure Functions • Run small pieces of code in Azure, without worrying about a whole application or the infrastructure to run it • Use your development language of choice • Pay only for the time your code runs and trust Azure to scale as needed • Open-source, available on GitHub
Azure Functions - Integrations Azure StorageAzure Cosmos DB Azure Service Bus Azure Event GridAzure Event Hubs Azure Mobile Apps Azure Notification Hubs GitHub On-premises Twilio
Developing a Function Go to Azure Portal Choose a trigger Choose language Code Add I/O bindings Save, test Monitor at runtime Compute -> Function App * (HTTP, Timer, Blob, Queue, Event Hub, Service Bus, etc.) (C#, F#, Node.js, Java, or PHP) To connect to data from within code * Functions can also be created using Visual Studio or Azure CLI
Hosting Functions Consumption Plan App Service Plan • Serverless • Automatically allocates compute power • Scales out and down as per load • No resources reserved in advance • Functions run on dedicated VMs like Web/API/Mobile Apps • Go for it if you: • Have underutilized VMs in other App Service Plans • Expect functions to run continuously • Need high CPU or memory • Expect functions to run longer than 10 minutes • Want to run functions on Linux
How Functions Scale
Functions – Use Cases 1 Order processing – scale per high/low loads (Black Friday, Super Bowl) 2 Send emails or text messages 3 Threshold alerts 4 Execute scheduled tasks 5 Process messages, documents, files when added 6 Respond to events in GitHub repository
Logic Apps
Logic Apps • Build, schedule, and automate processes as workflows to integrate apps, data, systems, and services across enterprises or organizations • Connect and integrate data within the cloud, on-premises, or both • Visual workflows, easy to use • Pay for what you use
Logic Apps - Connectors Built-in Actions • HTTP, Request, Schedule, API, Functions Integration Account Connectors • AS2, EDIFACT, Flat file, X12 Standard Connectors • Blobs, Event Hubs, Service Bus, Azure SQL DB, O365, Dynamics 365, Salesforce, Twitter Enterprise Connectors • MQ, SAP On-premises Connectors • SQL Server, BizTalk Server, SharePoint, Server, Oracle DB, DB2, File System Custom Connectors • REST based APIs
Creating a Logic App Go to Azure Portal Choose a template Choose a trigger Add steps Save, run manually Monitor at runtime Enterprise Integration -> Logic App * (polling / push) * Logic apps and custom templates can be created using Visual Studio • Action • Condition • Switch • Loop • Scope • Debatch • Recurrence • Request • HTTP • API • WebHook
Logic App – Use Cases 1 EAI/B2B Integration 2 Complex workflows involving SaaS solutions 3 Automatically respond to text messages or emails 4 Send/receive messages in a batch 5 Take action on negative tweets (sentiment analysis) 6 Exception Handling or Logging
Event Grid
Azure Event Grid Fully-managed intelligent event routing service that allows building serverless, event-based applications Listens and reacts to events, instead of polling Allows massive scaling, dynamically Pay per operation
Event Grid
Event Grid vs Event Hubs vs Service Bus Service Bus High-value, secure enterprise messaging Event Hubs Big data pipeline Event Grid Event-driven, reactive Asynchronous message delivery Captures, retains, replays event stream data Does not deliver data Allows batching, filtering, detecting duplicates, etc. Low latency, millions of events per second Serverless, dynamically scalable
Event Grid – Use Cases 1 Process images added to a blob storage container 2 Manage Azure subscription and resources 3 Stream big data to a data warehouse 4 Trigger Automation Runbook 5 Integrate application with other services
Serverless – Pros and Cons Pros • Reduced time to market • Lower operational and development costs • Near instant scalability without configuration • Increased developer productivity Cons • Lack of control • Security and performance issues due to Multitenancy • Not efficient for long-running applications • “Cold start” issues
Azure Event Grid with Logic Apps & Functions Demo
Q & A • Website: www.winwire.com • Email: marketing@winwire.com • Blog: http://www.winwire.com/blog-winsights/ • Twitter: @winwire

Azure Serverless with Functions, Logic Apps, and Event Grid

  • 1.
    Azure Serverless withFunctions, Logic Apps, and Event Grid Notes: • If you experience audio issues during the webinar, you can dial in through telephone details provided to you in your registration confirmation email. • Please feel free to post questions in the questions dialog & we will try to answer as many as we can at the end. • Recording of this session will be shared in next 24-48 hours. • You can also write to us at marketing@winwire.com for any clarifications or information.
  • 2.
    Session Speaker Viplove Sharma TechnicalArchitect WinWire Technologies
  • 3.
    3. Logic Apps 4.Event Grid 2. Azure Functions 5. Demo 1. Serverless Computing 6. Q & A Agenda
  • 4.
    Evolution of CloudComputing Data Centres Infrastructure as a Service (IaaS) Platform as a Service (PaaS) Container as a Service (CaaS) Serverless (FaaS) Software as a Service (SaaS)
  • 5.
    Serverless Computing An abstractionof servers, infrastructure and operating systems Dynamic allocation of resources, driven by events/triggers in near real-time Pricing based on actual consumption of resources Servers still required!
  • 6.
    Azure Serverless Fully managedservices ranging from compute, storage, database, orchestration, monitoring, analytics, and intelligence to help construct serverless applications for any kind of scenario Azure Functions Azure Storage Azure Cosmos DB Azure Active Directory Logic Apps Service Bus Event Grid API Management Event Hubs Azure Bot Service Cognitive Services Azure Stream Analytics Application Insights
  • 7.
  • 8.
    Azure Functions • Runsmall pieces of code in Azure, without worrying about a whole application or the infrastructure to run it • Use your development language of choice • Pay only for the time your code runs and trust Azure to scale as needed • Open-source, available on GitHub
  • 9.
    Azure Functions -Integrations Azure StorageAzure Cosmos DB Azure Service Bus Azure Event GridAzure Event Hubs Azure Mobile Apps Azure Notification Hubs GitHub On-premises Twilio
  • 10.
    Developing a Function Goto Azure Portal Choose a trigger Choose language Code Add I/O bindings Save, test Monitor at runtime Compute -> Function App * (HTTP, Timer, Blob, Queue, Event Hub, Service Bus, etc.) (C#, F#, Node.js, Java, or PHP) To connect to data from within code * Functions can also be created using Visual Studio or Azure CLI
  • 11.
    Hosting Functions Consumption PlanApp Service Plan • Serverless • Automatically allocates compute power • Scales out and down as per load • No resources reserved in advance • Functions run on dedicated VMs like Web/API/Mobile Apps • Go for it if you: • Have underutilized VMs in other App Service Plans • Expect functions to run continuously • Need high CPU or memory • Expect functions to run longer than 10 minutes • Want to run functions on Linux
  • 12.
  • 13.
    Functions – UseCases 1 Order processing – scale per high/low loads (Black Friday, Super Bowl) 2 Send emails or text messages 3 Threshold alerts 4 Execute scheduled tasks 5 Process messages, documents, files when added 6 Respond to events in GitHub repository
  • 14.
  • 15.
    Logic Apps • Build,schedule, and automate processes as workflows to integrate apps, data, systems, and services across enterprises or organizations • Connect and integrate data within the cloud, on-premises, or both • Visual workflows, easy to use • Pay for what you use
  • 16.
    Logic Apps -Connectors Built-in Actions • HTTP, Request, Schedule, API, Functions Integration Account Connectors • AS2, EDIFACT, Flat file, X12 Standard Connectors • Blobs, Event Hubs, Service Bus, Azure SQL DB, O365, Dynamics 365, Salesforce, Twitter Enterprise Connectors • MQ, SAP On-premises Connectors • SQL Server, BizTalk Server, SharePoint, Server, Oracle DB, DB2, File System Custom Connectors • REST based APIs
  • 17.
    Creating a LogicApp Go to Azure Portal Choose a template Choose a trigger Add steps Save, run manually Monitor at runtime Enterprise Integration -> Logic App * (polling / push) * Logic apps and custom templates can be created using Visual Studio • Action • Condition • Switch • Loop • Scope • Debatch • Recurrence • Request • HTTP • API • WebHook
  • 18.
    Logic App –Use Cases 1 EAI/B2B Integration 2 Complex workflows involving SaaS solutions 3 Automatically respond to text messages or emails 4 Send/receive messages in a batch 5 Take action on negative tweets (sentiment analysis) 6 Exception Handling or Logging
  • 19.
  • 20.
    Azure Event Grid Fully-managedintelligent event routing service that allows building serverless, event-based applications Listens and reacts to events, instead of polling Allows massive scaling, dynamically Pay per operation
  • 21.
  • 22.
    Event Grid vsEvent Hubs vs Service Bus Service Bus High-value, secure enterprise messaging Event Hubs Big data pipeline Event Grid Event-driven, reactive Asynchronous message delivery Captures, retains, replays event stream data Does not deliver data Allows batching, filtering, detecting duplicates, etc. Low latency, millions of events per second Serverless, dynamically scalable
  • 23.
    Event Grid –Use Cases 1 Process images added to a blob storage container 2 Manage Azure subscription and resources 3 Stream big data to a data warehouse 4 Trigger Automation Runbook 5 Integrate application with other services
  • 24.
    Serverless – Prosand Cons Pros • Reduced time to market • Lower operational and development costs • Near instant scalability without configuration • Increased developer productivity Cons • Lack of control • Security and performance issues due to Multitenancy • Not efficient for long-running applications • “Cold start” issues
  • 25.
    Azure Event Gridwith Logic Apps & Functions Demo
  • 26.
    Q & A •Website: www.winwire.com • Email: marketing@winwire.com • Blog: http://www.winwire.com/blog-winsights/ • Twitter: @winwire