How hackerspacemumbai/visage works
Project Type and Purpose
• Visage is a full-stack .NET solution for managing meetup registrations and check-ins, built with a microservices approach.
• It uses Aspire as the core framework, Blazor Hybrid for UIs (web, mobile, desktop), minimal HTTP APIs, EF Core for data access, and Azure Open AI for AI capabilities.
• It also includes a Node.js microservice for Cloudinary image signing.
Main Components
a. Frontends
• Blazor Hybrid Web (Web.Client, Web server-hosted)
• .NET MAUI mobile/desktop app (Android, iOS, MacCatalyst, Tizen, Windows)
• Shared component library (Visage.FrontEnd.Shared) used by all UIs
b. API Host
• Visage.AppHost – hosts minimal APIs, serves Blazor assets, hosts Node.js extension, applies Aspire DI, configuration, logging
c. Microservices
• Visage.Services.Eventing – event data, exposes minimal HTTP API, writes to EventDB
• Visage.Services.Registrations – registrant data, exposes minimal HTTP API, writes to RegistrantDB
• CloudinaryImageSigning (Node.js) – signs image upload parameters for front-end
d. Data Stores
• SQL-based EventDB (Eventing service)
• SQL-based RegistrantDB (Registration service)
e. External Services / Cloud
• Azure Open AI – NLP, AI services invoked by Aspire AI extensions
• Azure Container Apps (each microservice & AppHost containerized via Docker/Podman)
• Azure Monitor & Application Insights – monitoring and logging
• Cloudinary – media storage (via signed upload)
• (Optionally) Azure SQL or Cosmos DB for persistence
Relationships & Interactions
• UIs ▶ (HTTPS) ▶ AppHost minimal API endpoints (Aspire).
• AppHost ▶ (HTTP) ▶ internal microservices (Eventing, Registrations).
• UIs ▶ (HTTP) ▶ CloudinarySigning service (to get upload signatures).
• Microservices ▶ (EF Core) ▶ respective databases.
• AppHost / services ▶ (Azure SDK) ▶ Azure Open AI for NLP tasks.
• All containers ▶ (Azure Container Apps) ▶ deployed in Azure with environment variables and secrets.
Architectural Patterns & Principles
• Microservices: each bounded context (events, registrations, image signing) is its own service.
• Minimal APIs: lightweight HTTP endpoints, documented via Scalar OpenAPI and tested via .http files.
• Aspire Framework: centralized DI, configuration management, logging, resilience.
• Blazor Hybrid: share C# code across web and native clients.
• Containerization: Dockerized services for consistency across dev, CI, and production.
• Cloud-native: Azure services for AI, monitoring, and container hosting.