This document discusses serverless computing and Azure Functions. It asks common questions about managing servers like how often to patch and deploy code. It then introduces Azure Functions as an event-driven serverless computing platform that scales instantly based on demand and only charges for the resources used. Azure Functions allows code to run in response to events from sources like Azure Storage, Service Bus and HTTP requests. The document provides examples of common Azure Function triggers and bindings that integrate with other Azure services and external APIs. It also lists resources for learning more about Azure Functions like documentation, code samples and community support.
4. How often should
I patch my servers?
How can I increase server utilization?
How do I deploy new
code to my server?
Which packages should
be on my server?
It takes how long to provision a new server?
5. How often should I patch my servers?
How often should I backup my server?
Which packages should be on my server?
How many servers do I need?
How can I increase server utilization?
What is the right size of servers for my business needs?
How can I scale my app?
Which OS should I use?
How do I deploy new code to my server?
Who monitors my App?
6. How many “servers” do I need?
How can I increase “server” utilization?
What is the right size of “servers” for my business needs?
How can I scale my app?
7. How do I architect my app to become Serverless?
22. /// Function entry point. Review image and text and set inputDocument.isApproved.
[FunctionName("ReviewImageAndText")]
public static async Task ReviewImageAndText(
[QueueTrigger("%queue-name%")] ReviewRequestItem queueInput,
[Blob("input-images/{BlobName}", FileAccess.Read)] Stream image,
[DocumentDB("customerReviewData", "reviews", Id = "{DocumentId}")] dynamic inputDocument)