Microsoft Azure Functions – Part 1

Santosh Gaikwad

Connect on LinkedIn      Follow SCI Page

Write to
Santosh Gaikwad

Latest posts by Santosh Gaikwad (see all)

>> Part 2     >> Azure     >> O365

Introduction and problem statement.

Azure Functions is said to be evolution of Azure Web jobs, it is also referred as a server-less computing.

Many times we have a requirement of running small piece of code in cloud on trigger of certain events, equivalent to functions if compared to traditional way of programming, without really worrying about whole big application or really considering infrastructure architecture and with your favorite development language of choice, such as C#, F#, Node.js, JS, Python or PHP.

Azure Functions is a answer to the problem.

Benefits of using Azure Functions

Azure Functions lets you develop server-less applications using your choice of language C#, F#, Node.js, Python, PHP, batch, bash, or any executable.

Azure Functions supports NuGet and NPM, so you can use dependent libraries.

Azure Functions enables you to code functions, directly in azure portal or set up continuous integration and deploy through GitHub, Visual Studio Team Services.

Azure Functions enables you to pay only for the time your code runs.

Azure automatically scales infrastructure as needed to run the code.

Azure functions can be protected using OAuth with Azure Active Directory, Facebook, Google, Twitter, and Microsoft Account.

Different Types of Azure Functions

Azure functions provides flexibility to implements solutions on data processing, system integration, API integration, micro-services.

Functions provides default templates to get started as follows

HTTP Trigger: Trigger the execution of your code by using an HTTP request.

Timer Trigger:  Function that runs on a specified schedule.

Queue Trigger: Respond to messages as they arrive in an Azure Storage queue.

Blob Trigger: Process Azure Storage blobs when they are added to containers. Can use function for image processing or resizing.

Event-hub Trigger: Respond to events delivered to an Azure Event Hub, useful in Internet of Things (IoT) scenarios.

Service Bus Queue Trigger: Listen to message in queues.

Generic Web hook: Process web hook HTTP requests from any service that supports web hooks.

GitHub web hook: Respond to events that occur in your GitHub repositories.

Manual Trigger: A function that is triggered manually via the portal “Run” button.


>> Part 2     >> Azure     >> O365


Check Articles From Categories      Health and Parenting      Inspiring Stories      Technology      Microsoft Azure      SharePoint O365

Leave a Reply

Your email address will not be published. Required fields are marked *