Day-21 | Introduction to Serverless using Azure Functions ? Real Time Usecases #abhishekveeramalla

Summary

In this video, Abishek kicks off the Azure Zero to Hero series with a deep dive into serverless computing, focusing on its applications in DevOps. Over three episodes, the series explores serverless solutions for cloud cost optimization and security compliance. In Episode 21, Abishek explains the concept of serverless, debunking the misconception that it means 'no servers.' He showcases how serverless functions, like Azure Functions, can dynamically manage resources like blob storage, improving security and cost-efficiency. The series promises practical examples and essential skills for DevOps engineers, making it a must-watch for those looking to enhance their cloud management strategies.

Takeaways

• 😀 Serverless computing refers to dynamic provisioning and deallocation of servers, not the absence of servers.
• 😀 Developers may overlook security and cost guidelines, such as disabling public access and managing lifecycle policies for blob storage.
• 😀 A traditional solution for enforcing security and cost management involves writing scripts, but using a virtual machine for such tasks can result in high costs.
• 😀 Using serverless functions (like Azure Functions) can dynamically trigger actions only when required, reducing the need for constantly running virtual machines.
• 😀 Serverless functions only incur costs for the actual time they are running, offering significant cost savings compared to always-on virtual machines.
• 😀 An event-driven serverless model allows actions to be triggered based on specific events, such as the creation of Azure blob storage, ensuring compliance and automation.
• 😀 In a serverless setup, when an event occurs (e.g., blob storage creation), a function can automatically verify and enforce policies like disabling public access or managing lifecycle settings.
• 😀 Writing serverless functions with Python allows DevOps engineers to automate security and cost-related checks and corrections for cloud resources.
• 😀 Serverless functions are dynamically provisioned and deleted, saving maintenance efforts, unlike virtual machines that require continuous management.
• 😀 The upcoming videos in the series (Day 22 and Day 23) will delve deeper into cloud cost optimization and configuration management using serverless functions.

Q & A

What is the main focus of the Azure Zero to Hero series in this particular episode?

The main focus of this episode (Day 21) is to introduce the concept of serverless computing, explain why serverless is beneficial, and explore some DevOps-related use cases for serverless in Azure.

How does serverless computing work in Azure, according to the script?

Serverless computing in Azure involves dynamic provisioning and deletion of resources based on specific events, meaning resources are created when needed and discarded once their task is completed, minimizing costs and resource management.

What is the event-driven serverless model mentioned in the video?

The event-driven serverless model refers to triggering serverless functions based on specific events, like the creation of a blob storage. When the event occurs, an Azure function is triggered to execute the required actions, and resources are dynamically provisioned and then destroyed.

How does the script suggest handling security and cost issues related to blob storage in Azure?

The script suggests using Python scripts to verify if the blob storage meets security and cost requirements (such as disabling public access and managing lifecycle policies). Instead of running these scripts on a virtual machine 24/7, serverless functions are used to dynamically provision resources only when needed.

Why does the script recommend using serverless functions instead of virtual machines?

Using serverless functions reduces costs because Azure charges for the virtual machines 24/7, even when not in use. With serverless functions, resources are created dynamically based on events and destroyed afterward, ensuring that you only pay for the actual execution time.

What problem arises if developers ignore best practices for blob storage, and how does the script propose solving it?

If developers ignore best practices like disabling public access or managing the lifecycle of blob storage, it could lead to security risks and increased costs. The script proposes using serverless functions to automatically check and enforce these practices whenever a blob storage is created.

What is the advantage of using a serverless approach for managing resources like blob storage?

The advantage is that serverless functions are only invoked when needed, saving costs on resources that would otherwise be running continuously, such as virtual machines. This approach also reduces maintenance and operational overhead.

What will be covered in the next videos (Day 22 and Day 23) of the Azure Zero to Hero series?

In Day 22, the focus will be on cloud cost management and how a DevOps engineer can optimize cloud costs in an organization using serverless. On Day 23, the series will cover cloud configuration management, ensuring compliance with security and organizational guidelines, again using a serverless approach.

What is an example of a task that could be automated using a serverless function in Azure?

An example is automatically verifying whether a newly created blob storage has public access disabled and whether its lifecycle is configured according to the organization's standards. If not, the serverless function can correct the configurations automatically.

How does Azure charge for serverless functions and virtual machines, and what impact does this have on DevOps practices?

Azure charges for virtual machines 24/7, regardless of whether they're being actively used, which increases costs. In contrast, serverless functions are charged only for the actual execution time. This impacts DevOps practices by encouraging cost-efficient, event-driven resource management.