From 0cab80a3d86bb8a24e75136de1eb57667d543e3d Mon Sep 17 00:00:00 2001 From: Timna Brown <24630902+brown9804@users.noreply.github.com> Date: Wed, 1 Oct 2025 08:06:42 -0600 Subject: [PATCH 1/3] Enhance README with Azure Function App details Added detailed explanations about Azure Function App components and their roles. --- README.md | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/README.md b/README.md index f7ded1c..82c3605 100644 --- a/README.md +++ b/README.md @@ -46,6 +46,33 @@ Last updated: 2025-08-27 +> [!NOTE] +> - Azure Function App: This is the main service where your code lives and runs. Think of it as the container for your serverless functions. +> - You write small pieces of code called functions that respond to events—like HTTP requests, database changes, or scheduled timers. +> - These functions are event-driven or scheduled, meaning they only run when triggered, saving resources and cost. +> - App Service Runtime: This layer is the execution environment that powers your Function App. +> - Language Runtimes: Supports multiple languages like C#, JavaScript, Python, etc. +> - HTTP Framework / Middleware: Handles incoming HTTP requests and routes them to the correct function. +> - Application Insights: Monitors and logs telemetry data for performance and debugging. +> - Kudu / IIS: Manages deployment, diagnostics, and request/response handling. +> - Hosts Function App: This is the actual runtime that executes your function code. +> - App Service Plan: This is the infrastructure layer that supports the runtime. +> - Operating System: Can be Windows or Linux, depending on your configuration. +> - Temporary Storage: Uses `C:\Local\Temp\` for non-persistent file storage during function execution. + +
+ Centered Image +
+ +> [!TIP] +> When a trigger (like an HTTP request or a timer) fires: +> - The Function App receives the event. +> - The App Service Runtime processes it using the appropriate language runtime and middleware. +> - The function executes, possibly logging data to Application Insights. +> - The underlying OS and storage support the execution environment. + +`This setup allows developers to focus purely on writing code without worrying about servers, scaling, or infrastructure management—making Azure Functions a powerful serverless computing option.` + ## Scenarios 1. [High Decay test](./scenario1-high-decay): Test rapid temp file accumulation and disk decay From 5325d394ce3eb6d9f45c433682a8c7171a0d5263 Mon Sep 17 00:00:00 2001 From: Timna Brown <24630902+brown9804@users.noreply.github.com> Date: Wed, 1 Oct 2025 08:08:46 -0600 Subject: [PATCH 2/3] def arch --- .../FunctionApp Temp Usage - Diagrams.drawio | 111 ++++++++++++++++++ 1 file changed, 111 insertions(+) create mode 100644 _docs/FunctionApp Temp Usage - Diagrams.drawio diff --git a/_docs/FunctionApp Temp Usage - Diagrams.drawio b/_docs/FunctionApp Temp Usage - Diagrams.drawio new file mode 100644 index 0000000..e4dfbd5 --- /dev/null +++ b/_docs/FunctionApp Temp Usage - Diagrams.drawio @@ -0,0 +1,111 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + From 6d4f7ab4ceeae6f3ed792eaf35a06317461ea049 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Wed, 1 Oct 2025 14:09:11 +0000 Subject: [PATCH 3/3] Update visitor count --- README.md | 4 ++-- scenario1-high-decay/README.md | 4 ++-- scenario1-high-decay/terraform-infrastructure/README.md | 4 ++-- scenario2-optimized/README.md | 4 ++-- scenario2-optimized/terraform-infrastructure/README.md | 4 ++-- 5 files changed, 10 insertions(+), 10 deletions(-) diff --git a/README.md b/README.md index 82c3605..7969173 100644 --- a/README.md +++ b/README.md @@ -135,7 +135,7 @@ Last updated: 2025-08-27
- Total views -

Refresh Date: 2025-09-30

+ Total views +

Refresh Date: 2025-10-01

diff --git a/scenario1-high-decay/README.md b/scenario1-high-decay/README.md index 49f9805..4527344 100644 --- a/scenario1-high-decay/README.md +++ b/scenario1-high-decay/README.md @@ -147,7 +147,7 @@ Last updated: 2025-08-27
- Total views -

Refresh Date: 2025-09-30

+ Total views +

Refresh Date: 2025-10-01

diff --git a/scenario1-high-decay/terraform-infrastructure/README.md b/scenario1-high-decay/terraform-infrastructure/README.md index 059f2ce..ded8fe5 100644 --- a/scenario1-high-decay/terraform-infrastructure/README.md +++ b/scenario1-high-decay/terraform-infrastructure/README.md @@ -126,7 +126,7 @@ graph TD;
- Total views -

Refresh Date: 2025-09-30

+ Total views +

Refresh Date: 2025-10-01

diff --git a/scenario2-optimized/README.md b/scenario2-optimized/README.md index 7700ef9..be9cb9f 100644 --- a/scenario2-optimized/README.md +++ b/scenario2-optimized/README.md @@ -150,7 +150,7 @@ Last updated: 2025-09-05
- Total views -

Refresh Date: 2025-09-30

+ Total views +

Refresh Date: 2025-10-01

diff --git a/scenario2-optimized/terraform-infrastructure/README.md b/scenario2-optimized/terraform-infrastructure/README.md index 1531259..d05f621 100644 --- a/scenario2-optimized/terraform-infrastructure/README.md +++ b/scenario2-optimized/terraform-infrastructure/README.md @@ -126,7 +126,7 @@ graph TD;
- Total views -

Refresh Date: 2025-09-30

+ Total views +

Refresh Date: 2025-10-01