How londheshubham153/two-tier-flask-app works
This is a small Flask two-tier message app: users submit messages, the app stores them in MySQL, and the home page reads and renders them. The runtime excerpt shows the route-to-database and template flow; the README documents health checks and several ways to deploy the app. Deployment nodes represent those documented runtime options, not CI or build machinery. The deployment relationships are documented at a high level; their manifests and configuration were not sampled.
Main entry points: app.py Flask routes · docker-compose.yml Docker Compose · k8s Kubernetes setup · eks-manifests EKS manifests
Components 11
Web application
- Flask routes
app.py - Message page
templates/index.html
Message storage
- MySQL messages
Deployment options
- Docker Compose
docker-compose.yml - Container image
Dockerfile - Kubernetes setup
k8s - EKS manifests
eks-manifests
Cloud hosting
- Elastic Beanstalk
beanstalk - AWS deployment guide
aws
Other components
- Web user
- Health checker
Connections 15
- Web user → Flask routes: submits or views
README.md - Flask routes → MySQL messages: creates, reads, writes
app.py - Flask routes → Message page: renders
app.py - Flask routes → Web user: returns JSON or page
app.py - Health checker → Flask routes: checks /health
README.md - Docker Compose → Flask routes: runs app
README.md - Docker Compose → MySQL messages: runs database
README.md - Container image → Flask routes: packages app
README.md - Kubernetes setup → Flask routes: deploys app
README.md - Kubernetes setup → MySQL messages: deploys database
README.md - EKS manifests → Flask routes: deploys app
README.md - EKS manifests → MySQL messages: deploys database
README.md - Elastic Beanstalk → Flask routes: hosts app
README.md - AWS deployment guide → Flask routes: documents hosting
README.md - AWS deployment guide → MySQL messages: documents RDS
README.md