Skip to content

Commit 0cab80a

Browse files
authored
Enhance README with Azure Function App details
Added detailed explanations about Azure Function App components and their roles.
1 parent bc11207 commit 0cab80a

1 file changed

Lines changed: 27 additions & 0 deletions

File tree

README.md

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,33 @@ Last updated: 2025-08-27
4646

4747
</details>
4848

49+
> [!NOTE]
50+
> - Azure Function App: This is the main service where your code lives and runs. Think of it as the container for your serverless functions.
51+
> - You write small pieces of code called functions that respond to events—like HTTP requests, database changes, or scheduled timers.
52+
> - These functions are event-driven or scheduled, meaning they only run when triggered, saving resources and cost.
53+
> - App Service Runtime: This layer is the execution environment that powers your Function App.
54+
> - Language Runtimes: Supports multiple languages like C#, JavaScript, Python, etc.
55+
> - HTTP Framework / Middleware: Handles incoming HTTP requests and routes them to the correct function.
56+
> - Application Insights: Monitors and logs telemetry data for performance and debugging.
57+
> - Kudu / IIS: Manages deployment, diagnostics, and request/response handling.
58+
> - Hosts Function App: This is the actual runtime that executes your function code.
59+
> - App Service Plan: This is the infrastructure layer that supports the runtime.
60+
> - Operating System: Can be Windows or Linux, depending on your configuration.
61+
> - Temporary Storage: Uses `C:\Local\Temp\` for non-persistent file storage during function execution.
62+
63+
<div align="center">
64+
<img src="https://github.com/user-attachments/assets/4964fb4e-360c-4844-afda-7d0cddc1593c" alt="Centered Image" style="border: 2px solid #4CAF50; border-radius: 5px; padding: 5px;"/>
65+
</div>
66+
67+
> [!TIP]
68+
> When a trigger (like an HTTP request or a timer) fires:
69+
> - The Function App receives the event.
70+
> - The App Service Runtime processes it using the appropriate language runtime and middleware.
71+
> - The function executes, possibly logging data to Application Insights.
72+
> - The underlying OS and storage support the execution environment.
73+
74+
`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.`
75+
4976
## Scenarios
5077

5178
1. [High Decay test](./scenario1-high-decay): Test rapid temp file accumulation and disk decay

0 commit comments

Comments
 (0)