How shrutika-panchal/travel-memory-k8s works
Project type and purpose
• This is a full-stack “Travel Memory” web application that comprises a frontend UI, a backend API, a persistent database, and Kubernetes manifests for deployment, with an Azure Pipelines CI/CD workflow.
File structure
• Top level only shows project-wide configuration and k8s manifests:
• azure-pipelines.yml – CI/CD definition
• db-*.yaml (namespace, deployment, service) – PostgreSQL (or similar) DB setup
• pv.yaml & pvc.yaml – persistent storage for the database
• README.md, LICENSE, .gitignore
• (Implicit) we know there must be subdirectories such as /frontend and /backend containing the application code.
README
• Confirms “Full-Stack Solution with Backend, Frontend, and Kubernetes Deployment.”
• No further architectural details, so we infer a standard three-tier web app.
Main components
a. User’s Browser (Client) – interacts with the frontend over HTTPS
b. Frontend – single-page app (e.g., React, Angular) served from a container (Nginx, Node)
c. Backend API – REST/GraphQL server (Node.js/Express, Spring Boot, etc.) running in its own container
d. Database – PostgreSQL (or equivalent) in its own Kubernetes namespace, exposed via a ClusterIP Service
e. CI/CD Pipeline – Azure Pipelines orchestrating build, test, image push, and k8s deployment
f. Kubernetes Cluster – hosts frontend, backend, and database workloads
g. PV / PVC – Kubernetes PersistentVolume and PersistentVolumeClaim backing the database’s storage
Relationships & interactions
• Browser → Frontend: HTTPS request for UI assets and SPA routes
• Frontend → Backend: REST or GraphQL calls
• Backend → Database: SQL over the internal k8s Service endpoint
• Azure Pipelines → Container registry → Kubernetes API (for rolling updates)
Architectural patterns
• Three-tier (Presentation / Business / Data)
• Infrastructure as Code (all k8s objects declared in YAML)
• Continuous Delivery via Azure Pipelines
Key technologies & frameworks
• Frontend: React/Angular/Vue, served by Nginx or Node
• Backend: Node.js/Express (or similar)
• Database: PostgreSQL (namespace + service + PVC)
• Kubernetes: Deployments, Services, PV/PVC
• CI/CD: Azure DevOps Pipelines