3.6 Introduction to Serverless Computing

Video Activity
Join over 3 million cybersecurity professionals advancing their career
Sign up with
Required fields are marked with an *

Already have an account? Sign In »

19 hours 58 minutes
Video Transcription
Welcome back. In this episode, we're going to take a look at some azure offerings in relation to serve Earless computing.
My objectives include for you to first understand so wireless computing and then look at some of the azure offerings related around this concept.
This includes logic APS as your Functions Service bus and of Ingrid.
As always, we're going to start off with the question. What is serverless computing?
If you've never heard of it before, the name itself can be a little confusing. How can you have computing power without servers?
Well, they're still servers involved, but you don't have to worry about them. Instead of building servers and installing the operating systems and configuring software dependencies, you don't have to worry about that.
Several is computing is where you as the IittIe professional, don't have to worry about managing servers here. You only have to worry about developing the code while azure well provisioned the necessary infrastructure and manage it for us.
Basically, the underlying components, such as servers and operating systems, are abstracted where we really don't care what's running beneath the app.
What's great is if your application requires more resource is the several ist compute can instantly scale and adapt to changing workload. Request. This means you don't have to panic and provisioned. War resource is yourself when it could be done automatically and instantly. Another great feature is you only pay for when your code is running.
This greatly differs from the model of an application running on virtual machine.
Even if you have a small virtual machine hardware profile, you're still paying for that compute power, even if your code isn't running, not the case with server Lis you only pay for the resource is whenever your coat is executed.
Now that's the basics of service computing. If we look at our exam objectives for the A C 300 there are just a few of the azure service offerings that it focuses on. The rest of this episode will take a look at each of these four offerings.
First, let's discuss logic. APS Logic. APS allow you to build work flows and business processes that require connecting to multiple data, sources and applications. The logic app workflow looks a lot like a flow chart where we can visualize it and we could have multiple branches of logic based on decision points during execution.
You might see other solutions like this identified or described as if this, then that meaning. If this happens, then we're going to take this action. Logic gaps use connectors, which can connect azure office through 65 Service's and other third parties. Service is like ASAP and sales force.
These connectors can be used to start a logic, app or process in action during the workflow
logic. Gaps are based on triggers, which is when a specific event happens or when new data is available inside a service. You can also scheduled the start of a logic app if he only needed to periodically run. The workflow
actions occur after the trigger, and our steps in the workflow actions usually correspond to an operation that performs some functionality against a connector or other service, like sending an email or posting a tweet on Twitter Logic. APS are great because you don't have to build the code behind connecting two different data sources.
These connectors are managed by Microsoft and other vendors.
It also follows the concept we learned about and server this computing and that it follows a consumption based model where you only pay for what she used
here have a screen shop of the logic apse, a designer and, well, Seymour. In this and demos and later episodes, you can see where we have a trigger of when a new tweet appears. Then we have some additional actions, like getting the user information of the person who made the tweet and then sending an email to Outlook.
Our next service offering is as your functions. These allow for running small bits of code. If you look at functions from typical programming practices. Functions are parts of a program that perform specific task within the larger application base
as your functions allow for riding the code that you need to accomplish a task without worrying about writing out an entire app to use it
or to configure the infrastructure to host it on
in line with serverless compute concepts, you don't have to worry about dynamically allocated Resource is if your function sees more usage and you can use a consumption payment model where you only pay for executions of the APP
as your function supports several different programming languages like C sharp, Java, JavaScript, power shell and python.
You also have your choice of running the function app on Windows or Linux systems.
So the idea behind function APS is creating small bits of code that you can dynamically execute when needed. For example, we looked at logic APS on the previous slides. If there are no actions that meets your needs when creating logic app, you can then call an azure function to complete the task for you.
This starts the introduction and the idea that we can chain together different service offerings inside of Azure to build more complex work flows.
Here we have an example of a function inside of Azure, and this first trigger that we have here is an http trigger, which is just when we access the function. Muriel, we're going to display a message to the screen, and we will see more details about this in our demo episode.
Next is at your service bus as your service bus is a messaging platform used to ensure a synchronous data transfer between applications and service is
this data is transferred using what is called a message which can be in Jason XML or text format. Now, the idea of this service bus seems a little abstract, so let's think of some examples. You could use Azure Service bus for transferring business transaction data from one service to another,
like sales are purchase orders or updating inventory management systems.
This works by putting those messages into Q's, where they can wait until the receiving application can receive the message and process it. In addition to processing these messages, you could also set up topics to send and receive multiple messages. Topics are used in a scenario where multiple applications or receivers can subscribe to a single topic.
This provides a one too many communication possibility. A message is sent to a single topic than each subscriber can take that message and perform their own action on it.
The topic concept is slightly different from the service bus queue, and that message is in a queue are on Lee processed by one consumer or application, whereas you can have multiple subscribers to a single message in a topic.
Service Bus has a few advanced features, and I want to touch base on a few of those Right now. The first is scheduled delivery, which allows for submitting your messages into a queue. For delayed processing,
you might have a bunch of messages in acute that you want to schedule a job to process those messages at a certain time. The next is batch ing, where the Q delays sending a message for a certain period of time.
Any messages received during that time period are held in the queue, and then they're transmitted in batches to the receiver. Finally, there is dead lettering, which means the key. You will hold on to messages that cannot be delivered or processed. At that moment.
The dead letter Q is separate from the main Q, which allows for removing inspecting these messages that could not be processed and then resubmitting them. You can also set a time to live and remove the message if it cannot be processed in the time of the manor. Over here on the right, we have a screenshot of creating a Q, where you can see some of these messages, such as the time to live
a locked oration
or enabling dead lettering on message expiration.
Next, we have event grid, which allows building applications that are based on event driven architectures. You can subscribe to azure resource is and then trigger an event handler such as an azure function, logic app, Web hook in point or azure automation So you can see we're taking some of the previous
serverless concepts, and we're tying them into the event. Great here.
Some scenarios for event grid include when an image is uploaded to a blob storage container, you can trigger an Asher function and then analyze the image or when a virtual machine is provisioned. Event good can detect this new resource and use azure automation to make sure the virtual machine is configured correctly.
And here I have just a little diagram kind of showing the idea behind a vin cred on the left. We have different events sources like blob storage, resource groups or subscriptions, those air ingested by the invigorated. And then they're sent onto event handlers, where you might trigger an azure function, a logic AB or a storage Q.
Or as your automation
you can kind of start to see on the left hand side. We have a lot of these. Resource is we've been working with so far on this course, and on the right, we have some of these server lis concepts. We've just learned about it in this episode to act on those sources
that does it for introduction to serve Earless computing.
Next, we're going to jump into the azure portal and take a look at how to configure logic, app and our logic app Demo.
See you in the next episode.
Up Next