How bmoussaud/azure-rambi works
Project Type & Purpose
• Azure Rambi is a cloud-native, microservices-based full-stack application for generating, storing, and browsing AI-generated movie data (titles, plots, posters, galleries).
• It leverages Azure Container Apps for service hosting, Azure API Management (APIM) as the gateway, multiple Azure PaaS services (OpenAI, DALL-E, Redis, Cosmos DB, Event Hubs, Blob Storage, Key Vault, App Insights), Dapr for local dev, and Bicep for infra as code.
Main Components
a. Frontend (gui-svc)
• Python Flask app, served from Azure Container Apps.
• Static pages call backend over APIM.
b. API Gateway (APIM)
• Ingests all client calls, applies policies (TMDB, OpenAI), routes to container apps.
c. Microservices (Azure Container Apps)
• movie-generator-svc (FastAPI): calls Azure OpenAI to generate new movie ideas, uses Redis for caching/state.
• movie-poster-svc: calls DALL-E/OpenAI for poster images, stores metadata in Blob Storage or Cosmos DB.
• movie-gallery-svc: retrieves stored movies/posters, exposes browsing API, persists data to Cosmos DB.
d. Azure PaaS Services
• OpenAI (GPT-4, O1-mini) & DALL-E for language/image generation.
• Redis Cache for session/state management.
• Cosmos DB for persisting movie metadata.
• Blob Storage for poster image storage.
• Event Hubs / Dapr pub-sub for event-driven updates (e.g., gallery updates).
• Key Vault for secrets.
• App Insights for monitoring/tracing.
e. Supporting Infrastructure
• Azure Container Registry (ACR) for Docker images.
• Bicep modules under infra/ to provision all Azure resources.
• GitHub Actions pipeline to build, push images, deploy infra and services.
Relationships & Data Flows
• User → GUI (HTTPS) → APIM
• APIM → Microservices (via HTTPS, with Dapr sidecar locally)
• movie-generator-svc → OpenAI → returns JSON movie data → may publish events to Event Hubs / Dapr pub-sub → movie-gallery-svc subscribes
• movie-poster-svc → DALL-E → stores image in Blob Storage → updates Cosmos DB
• movie-gallery-svc → Cosmos DB / Blob Storage (reads metadata & image URLs)
• Services → Redis for caching / state (via Dapr state store in dev)
• All services → App Insights for telemetry
• GitHub Actions → ACR (push) & Azure infra (Bicep deploy) & Container Apps (deploy)
Architectural Patterns & Principles
• Microservices: independently deployable services per business capability
• Containerization: Docker + Azure Container Apps
• API Gateway pattern: APIM fronting all services
• Event-driven: pub/sub via Dapr or Event Hubs for decoupling generator and gallery
• Infrastructure as Code: Bicep modules for repeatable provisioning
• Sidecar / Dapr: local development parity for state, pub/sub
• Separation of concerns: distinct UI, compute, storage, and AI layers