How ronaldbosma/azure-integration-services-quickstart works
Project Type and Purpose
• This repository is an Azure Integration Services “Quickstart” template. It’s a combined Infrastructure-as-Code (IaC) solution (using Bicep modules) plus a sample application (an API, Azure Function, and Logic App) designed for demos, experimentation, and CI workflows.
• The template deploys a set of Azure services (API Management, Function App, Logic App, Service Bus, Event Hubs namespace, Key Vault, Application Insights, Storage Account) and wires them up so that a message can be published via an API, processed by both a Function and a Logic App, and stored in Table/Blob storage.
File Structure & Architectural Patterns
• infra/
• functions/ – Bicep user-defined functions (naming conventions, helpers, tests)
• modules/
– application/ – application-specific resources (API in APIM, Service Bus topic/subscriptions, Storage table & container)
– services/ – modules for each Azure Integration Service (api-management.bicep, function-app.bicep, logic-app.bicep, service-bus.bicep, event-hubs-namespace.bicep, storage-account.bicep, key-vault.bicep, app-insights.bicep, etc.)
– shared/ – reusable modules (role assignments, app settings merge)
• main.bicep & main.parameters.json – top-level orchestration of included services
• src/
• functionApp/ – C# Azure Function project triggered off Service Bus messages, writes to Table Storage
• logicApp/ – Logic App Standard workflow triggered off Service Bus messages, writes to Blob Storage
• tests/tests.http – REST Client calls to the deployed API (publish message, get from table, get from blob)
Key Components & Interactions
a. Client → API Management
• HTTP POST “publish” call with subscription key
• HTTP GET calls for table-stored and blob-stored messages
b. API Management → Service Bus Topic
• APIM policy/back-end routes request to Service Bus topic
c. Service Bus Topic → Two Subscribers
• Azure Function (Consumption, .NET 9 isolated)
• Logic App Standard (WS1 tier, custom .NET code runtime)
d. Function App writes message to Storage Account Table
e. Logic App writes message to Storage Account Blob Container
f. Supporting services:
• Key Vault (stores APIM subscription key secret, referenced by Function & Logic App)
• Application Insights (logging & telemetry for API Management, Function, Logic App)
• Event Hubs namespace (optional, only if included)
Architectural Patterns & Principles
• Serverless / event-driven & pub/sub: Service Bus topic with multiple subscribers
• Infrastructure as Code: Bicep modules for services, application, shared functions, types
• Separation of concerns:
• “services” layer (all Azure services modules)
• “application” layer (resources for the sample app)
• “functions” layer (IaC helper logic)
• “code” layer (Function App + Logic App workflows)