How jmpompeo/compoundinterestcalculator works
Project type and purpose
• From the file tree and (admittedly sparse) README, this is a serverless/.NET Azure Function project named “CompoundCalc” designed to calculate compound interest. It includes:
• A Function App (“CompoundCalculator”) implemented in C#
• Supporting business-logic services and helpers (Conversions.cs, CalculationService.cs)
• Infrastructure as code (Bicep templates under .infrastructure) to deploy the Function, Storage account, and Application Insights
• A test suite (CompoundInterestCalculatorTests)
• CI/CD workflows (GitHub Actions), PowerShell scripts, and Dockerfiles for local and test containerization
File structure
• Top-level directories:
• .infrastructure – Bicep modules: app-insights.bicep, function-app.bicep, storage.bicep
• CompoundCalc – the Function App source:
– Functions folder (HTTP trigger entry point)
– Services & Helpers (business logic)
– Models/Requests (data contracts)
• CompoundInterestCalculatorTests – unit tests mirroring the Function App’s code structure
• .github/workflows – CI/CD definitions (build, deploy, deploy_bicep)
• Scripts – automation helpers (export-template.psm1, test-func.psm1)
• Key config/build files:
• CompoundInterestCalculator.sln
• Dockerfile & Dockerfile.tests
• global.json, host.json, launchSettings.json
README for additional insights
• No architecture section present yet. We’ll infer from code and infra.
• The project uses Azure Functions, Bicep for infra, GitHub Actions for CI/CD, and .NET 6/7 SDK (global.json).
Detail without over-splitting
• Internal layering of the Function App: Trigger → Services → Helpers → Models
• Test suite and containerization as side-bars rather than main data flows