Module 2ab - Exploring Azure Core Products - Compute, Functions & Logic Apps Flashcards

1
Q
  • What are Azure Functions?
  • What kind of work are they most common for?
A

Serverless Compute, PaaS offering ideal when you’re only concerned about running code

  • Allows you to execute code in almost any modern coding language
  • Common for Event responses, timer responses, or dealing with messages from other Services
  • When work can be done quickly (seconds or less)
  • Flexibility allows for managing scale, run on virtual networks or totally isolate the function
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What two (2) types of Function Apps are available?

A

Stateless - The default type for all. The function does not maintain state

Durable - Or stateful, by passing a context through the function to track prior activity

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the two (2) cost models for Function Apps

A

Consumption - pay for CPU cycles used per execution. Extremely cheap

Execution - pay per call. Significantly higher cost per unit but it’s something like 20 cents per one MILLION executors …

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What are Azure Logic Apps?

A

Power App Platform Serverless Compute Service

  • Instead of executing CODE, these execute WORKFLOWS built with predefined logic blocks
  • They start by trigger; either Event or new data meets specific criteria
  • Basic scheduling triggers for running workflows on a regular interval

You can create logic app workflows through the Azure Portal Visual Designer, which are persisted as a JSON file

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Hint: the *concept*, not the implementation…

Functions vs Logic Apps: What’s the main diff wrt Development and performing actions?

A

Functions are Code-First (Imperative). You write code to complete steps/actions

Logic Aps are Designer-First (Declarative). You use a GUI to define actions and how they relate to each other

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Functions vs Logic Apps: What are the diffs wrt state?

A

Functions are stateless, though Durable Functions can have state via Execution Context

Logic Apps are stateful and can pass state and results to the next steps in their workflow

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Functions vs Logic Apps: What’s the diff wrt Binding and Connectivity?

A

Functions have about a dozen built-in binding types, ability to write custom bindings

Logic Apps have a large collection of connectors, Enterprise Integration Pack for B2B scenarios and the ability to build your own custom connectors

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Functions vs Logic Apps: What tools Monitor each?

A

Functions are monitored by Azure Application Insights

Logic Apps can be monitored through Azure Portal or Log Analytics

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Functions vs Logic Apps: How is each managed ie what would you use to interact with each one?

A

Functions can be accessed through their REST API or through Visual Studio

Logic Apps can be accessed from Azure Portal, a REST API, Powershell, or through Visual Studio

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Functions vs Logic Apps: What are their respective Execution Contexts ie where does each Service run?

A

Functions can run locally or in the Cloud

Logic Apps ONLY run in the Cloud

How well did you know this?
1
Not at all
2
3
4
5
Perfectly