• All source code except security files is stored in Github, and when code is updated from the local machine, Actions are triggered for each branch to execute the Jenkins Pipeline, and the build/deployment process of docker images proceeds based on the Jenkinsfile in the source code.
• The pipeline proceeds in the order of update file download → source code transpiling → docker image build → deployment → cleanup, through which both backend and frontend services are updated.

• Build files are stored through a private docker registry, and access is restricted through docker login. Docker login permissions are granted to each developer's local machine, Vault Server, and Kubernetes Cluster.
• The docker images for the frontend and backend services are stored separately, and the storage capacity is reset periodically for management.

• Edge servers are infrastructure deployed on physically installed local servers that perform partial or cache-level roles of application infrastructure deployed in the cloud.
• The components on the edge server are configured for application deployment and maintenance based on docker-compose, and for traffic routing through tunnels.

• Database and cache servers are recommended to operate with a minimum of 3 replica sets, but currently operating with 1 replica.
• The backend service is configured as Monolithic, but is operated separately as batch mode and service mode, and the service mode is scaled/shrunk according to the traffic.
• The frontend service operates a container built with Nextjs, and scales/shrinks the container according to the traffic. (CPU Intensive)

• The Vault server operates as a local server, allowing only authorized users to upload/update/download env and secrets needed for development. It also builds Docker images and registers them in the registry.
• Acts as a build environment for Jenkins deployment, performing non-periodic CPU-intensive build processes and dockerization. The completed docker image is pushed to the Master server's registry for updates.