Implementing Functions Flashcards
1
Q
Features of a Function App
A
- A serverless application platform
- A simple way to run small pieces of code “functions” in the cloud
- Auto Scaling to meet demains
- Under the consumption plan, you only pay when its running
2
Q
What are the various hosting choices
A
- Consumption Plan (Serverless, automatic scaling with 5 minute limit)
- App Service Plan (Traditional pricing model)
- Premium Plan (speed, security reserved instances)
- Docker Containers (on premises or in any cloud)
- Locally (for development and testing)
3
Q
What are the choices for development tools
A
- Portal
- Visual Studio
- Azure Function Core Tools (Cross-platform CLI and Visual Studio Code)
4
Q
Function Trigger Types Examples
A
- HTTP Request Triggers
- TImer Triggers
- Queue Triggers
- CosmosDB Trigger
- Blob Triggers
- And Many others
ONLY ONE TRIGGER PER FUNCTION
5
Q
Authentication Key Types
A
- Anonymous (no key required)
- Function (key per function
- Admin (key per Function App)
6
Q
What are the characistics of an Input Binding
A
- Get data into our functions
- Optional
- A binding is connection to data
- Can have multiple input bindings
Examples include Blob, CosmosDB, Microsoft Graph
7
Q
What are the characistics of an Output Binding?
A
- Lets us write data to an external system
- Can have more than one output binding
Examples include Creating a new blob, post a message to a queue, creates a new document in CosmosDB
8
Q
Azure Durable Functions
Name 3 types of functions in Durable Functions
A
- Client or Starter Function (calls the Orchestration function)
- Orchestration Function (defines the steps in the workflow and handle errors)
- Activity Function (implements a step in the workflow process
9
Q
Information
- The orchestrator function handles all errors from the various steps
- Can run sequentially or in parallel
- Activity Functions can use any of the input and output bindings
A
10
Q
Name the 5 Orchenstration Patterns
A
- Function Chaining
- Fan-out Fan-in (parellel processing)
- Asynchronous HTTP API (good for repeatly pull for progress)
- Monitor (recurring porcess in a workflow)
- Human Interaction
Need to better understand Asynchronous HTTP API and Monitor differences