How harshashiyani/two_tier_app_using_docker_and_jenkins works
This repository documents a Dockerized Java/Spring Boot and MySQL application, with Jenkins automating deployment to AWS EC2. The documented flow runs from a code push through GitHub and Jenkins to deployed application and database containers. The README does not describe request handling inside the application, so the graph keeps that runtime as a single component rather than inferring links among its source files. It also inconsistently calls the deployed application Flask; the architecture diagram identifies Java/Spring Boot.
Main entry points: Jenkinsfile Jenkins pipeline · DemoApplication.java Spring Boot app · init.sql MySQL container · docker-compose.yml Compose deployment
Components 8
Deployment automation
- Jenkins server
- Jenkins pipeline
Jenkinsfile - Compose deployment
docker-compose.yml
Application runtime
- Spring Boot app
src/main/java/com/example/demo/DemoApplication.java - MySQL container
init.sql
Other components
- Developer
- GitHub repository
- AWS EC2
Connections 9
- Developer → GitHub repository: pushes code
README.md - GitHub repository → Jenkins server: supplies source
README.md - Jenkins server → Jenkins pipeline: runs pipeline
README.md - Jenkins pipeline → GitHub repository: clones repository
README.md - Jenkins pipeline → Compose deployment: runs Compose
README.md - Jenkins server → AWS EC2: deploys on
README.md - AWS EC2 → Spring Boot app: hosts container
README.md - AWS EC2 → MySQL container: hosts container
README.md - Spring Boot app → MySQL container: uses database
README.md