Technical Architecture Purpose of the Model This model illustrates the end-to-end technical flow and hosting topology for the Supplier Service domain within the Ea-2-Sa environment. It captures how a front-end SPA (ea2sa website and CRM SPA) interacts with backend microservices (Supplier-service API and Supplier service), the infrastructure on which these components are deployed (AWS S3, Dell PowerEdge, and Kubernetes), and the deployment artifacts (YAML manifests) that govern the operational lifecycle of the microservice. The primary purpose of the model is to provide: 1. A clear view of system deployment locations across cloud and on-prem environments. 2. An understanding of API integration pathways from SPA applications to backend microservices. 3. Visibility into the CI/CD and deployment pipeline, highlighting how Kubernetes manifests connect the supplier service to the production cluster. 4. Traceability from user-facing applications down to operational infrastructure, supporting both solution design and operational readiness. 5. A reference model for future microservice expansion, demonstrating a repeatable architecture pattern (SPA → API → microservice → cluster).