How to create a Function App on Cosmos DB

Editor's Notes

• #4: You don’t need a server to compute or run your funcation, and no need to worry about the infrastructure, you can focus only about the functionality you want to write You can scale the resources of your function when its needed, initially plan for something simple and you can scale it when its needed You can focus on building your application, no need to worry about maintaining servers when your workload grows, you can scale it on demand, when its required You can select a familiar language to build up the function, Javascript, C#, Java, scripting language like Python, Php, bash, batch and powershell. You can use web based interface to write the code or can upload a precompiled code, You can use continuous deployment to integrate with your deployment pipeline
• #5: You can interact with different Azure and external services, Easily interact with Azure CosmosDB, storage, eventhub, eventgrid, notification hub. Servuce bus, and external services like Twillio, SendGrid, github You can save cost and maintain less code
• #7: Timer – evenet based on timer, execute code every 15 mins to clean up the database table based on a custom logic written in a function Azure service event processing – trigger an event based on an activity in azure service, execute log file in a blob and transform into a row in sql db Serverless web app – function can act as a single page app, app calls function using webhook url, save data, read data and decide what to do Serverless mobile backends – mobile app capture an image and call a function to resize the image to be mobile friendly Real time stream processing – IOT device send message to streat analytics and call a function to process and save data into a sql db Real time bot messaging – Create a function that processes a message using cortana analytics and call it using ms bot framework
• #8: Automatically allocates compute power when your code is running, you are charged for compute resources only when your function is running, You can scale out when load increases, and scale down when code is not running, no need to pay for idle VMs pay only when your function is running Billing based on no of executions, execution time and memory Similar to web apps, API apps, mobile apps dedicated vms are allocated to your app service apps Function host is always running, When your app need to run continuously, app sevice plan is cost effective When you need more cpu and memory that what is provided in consumption plan You need to run longer than maximum execution time allowed in consumption plan (10 mins) When you want to run your function apps on linux, or you want to provide a custom image on which to run your functions