How vishalkurane/tajrestaurant works
Project type and purpose
• This is a cloud-native, microservice-based full-stack application (“Taj Restaurant App”) for restaurant management.
• Two logical subsystems:
• User-facing operations (“Taj-User-App”, 5 Flask microservices)
• Administrative operations (“Taj-Admin-App”, 4 Flask microservices)
• An Azure Functions-based Python API layer for core CRUD and authentication, backed by Azure Service Bus and Azure SQL Database.
File structure
• Top-level folders:
• APIs: Python Azure Functions folder with one function per path (AddUser, UserLogin, ValidateToken, etc.)
• App: Subfolders for each microservice in AdminApp and UserApp, each with its Dockerfile, Flask app.py, static + templates
• Database: SQL DDL files (Create_*Table.sql, triggers)
• Terraform: IaC for Function App, Service Bus, AKS, Application Insights
• Yaml Manifests & Helm Repos: Kubernetes manifests & Helm charts for deploying microservices, monitoring, logging
• This shows a microservices + serverless hybrid architecture deployed on Azure Kubernetes Service (AKS) and Azure Functions.
README for additional insights
• Confirms microservices count, cloud components (Azure Functions, Service Bus, Azure SQL, AKS)
• Monitoring/Logging with Prometheus/Grafana and EFK (Elasticsearch, FluentBit, Kibana)
• Deployment via Helm charts (TajAdminApp, TajUserApp, Monitoring) and YAML manifests
Main components
a. Clients / Frontends
• Web browsers (User UI, Admin UI)
• Labeled “Taj-User-App UI” and “Taj-Admin-App UI”
b. API Layer
• Azure Function App (Python 3.11)
c. Service Bus
• Azure Service Bus Namespace & Reservation Queue for asynchronous booking messages
d. Microservices (AKS Namespaces)
• Namespace: taj-user-app – 5 Flask microservices (Auth, Home, Menu, Reservation, Auth-CreateAccount)
• Namespace: taj-admin-app – 4 Flask microservices (AdminAuth, AdminHome, AdminMenu, AdminReservation)
e. Data Storage
• Azure SQL Database (single logical instance)
• Tables: UserTable, AdminTable, MenuTable, ReservationTable
f. Infrastructure / Orchestration
• Helm Charts & YAML manifests – show them as deployment artifacts feeding AKS
g. Monitoring & Logging
• Monitoring namespace: Prometheus + Grafana + Alertmanager
• Logging namespace: Elasticsearch + FluentBit + Kibana (EFK)
h. CI/CD & IaC
• Terraform – provisions Function App, Service Bus, AKS, Application Insights
• Azure DevOps Pipelines – deploy Helm charts for microservices & monitoring
Relationships and interactions
• Clients → Ingress (AKS Nginx) → Flask microservices → Azure SQL
• Flask microservices → call Azure Functions APIs for CRUD & JWT token validation
• Azure Functions → read/write to Azure SQL; send messages to Service Bus for bookings
• Reservation microservice → consumes messages from Service Bus asynchronously
• Kubernetes pods emit logs → FluentBit → Elasticsearch → Kibana
• Monitoring stack scrapes metrics from pods → Prometheus → Grafana
Architectural patterns & design principles
• Microservices pattern (each service independent, containerized)
• Serverless functions for a stateless API façade
• Event-driven async communication via message queue
• Centralized logging and monitoring
• Infrastructure as code (Terraform, Helm)
Technologies to call out
• Python Flask, Docker, Azure Kubernetes Service, Azure Functions, Azure Service Bus, Azure SQL Database
• Helm charts, Kubernetes YAML manifests
• Terraform, Azure DevOps pipelines
• Prometheus/Grafana, Elasticsearch/FluentBit/Kibana, Azure Application Insights
Essential details to capture
• Names and counts of microservices
• JWT authentication flow via ValidateToken function
• Booking workflow: UserUI → API → Service Bus → Reservation microservice → SQL
• Deployment artifacts: Terraform & Helm feeding into AKS and Azure Functions
• Monitoring & logging pipelines