How dvillanuevav/portafolio-management works
Project type and purpose
• This is a back-end portfolio management solution composed of:
• A .NET Web API (“API” project) for CRUD and read operations on portfolio balances and share-price records.
• A collection of Azure Functions (“Functions” project) that perform background jobs:
– Balance computation at day’s end (timer-trigger & HTTP-trigger).
– Processing new deposit messages from an Azure Storage Queue.
– Maintaining an in-memory Redis cache of daily share-price quotas via Cosmos DB change feed.
• A shared “Common” library for domain entities, validation, and settings.
• Azure resources: Cosmos DB (NoSQL), Azure Storage Queue, Redis Cache.
File structure
• Top-level:
• src/API – Web API endpoints subdivided by feature (Balances, SharePrices).
• src/Functions – Azure Functions grouped by feature (Balances.Compute, Deposits.Compute, SharePrices.WriteThroughCache).
• src/Common – Shared domain models, validators, settings classes.
• tests – Unit tests targeting Azure Functions.
• Infrastructure/config:
• API/appsettings.json & Cosmos/Redis connection strings.
• Functions/host.json, local.settings.json, serviceDependencies.json for emulator connectivity.
• launchSettings.json for local debugging.
README for additional insights
• Dependency list: Azure Cosmos Emulator, Azurite, Redis.
Elements
• Data stores in another (e.g., orange).
• Clients/API in a third (e.g., blue).