How pandugaluh/blog-azure-blob-storage works
• API Service (AzureBlobAPI) – This is the core component and contains:
• Entry point (Program.cs) where the application starts.
• Configuration and settings management (BlobSettings via appsettings.json files).
• Helper functions (under Helpers, such as FileExtentions.cs).
• Domain models (under Models folder: BlobDetail, BlobRequest).
• Presentation layer (under Presents, e.g., BlobPresents) which formats responses.
• Service layer (under Services: BlobStorage service and its interface IBlobStorage) implementing business logic.
• External Dependency – Azure Blob Storage itself should be represented as an external system. Mark it as a cloud resource that the API communicates with.
• Factory Extensions – The AzureClientFactoryBuilderExtensions in the project indicates a factory or extension pattern for constructing Azure client instances. Represent this as a supportive component that aids in initializing external service clients.
Component Relationships and Interactions
• API Service sending requests to the BlobStorage service located in the Services layer.
• The BlobStorage service will use the factory extension (AzureClientFactoryBuilderExtensions) possibly to build a proper client for connecting with Azure Blob Storage.
• Models and Present classes showing their roles in handling data (input/response shaping).
• Configuration management (Settings) feeding into the initialization and configuration of the API and its services.
– Data flow from client requests arriving at the API.
– Business logic applied by Services.
– External calls from the BlobStorage service to the Azure Blob Storage.
– Responses flowing back through the presentation layer (Presents) to the client.
Architectural Patterns and Design Principles
• Separation of Concerns: Distinct modules for handling logic (Services), data (Models), utility functions (Helpers), and presentation (Presents).
• Dependency Injection / Factory Pattern: Use of client factory extension patterns for creating Azure clients.
• Configuration-Driven Behavior: Manage settings centrally via appsettings.json, indicating adherence to configurable and environment-based deployments.
Incorporating Technologies and Frameworks
• .NET Framework/Core is the underlying technology.
• Azure Blob Storage acts as the external cloud datastore.
• The specific extension methods and configurations point towards a modular and testable architecture.