About the client
The client sells aftermarket spare parts and needed a digital sales channel that could grow with customer demand without growing its operational workload. FiftyFive was engaged to design, build and deploy the customer portal from the ground up, with the infrastructure automated from the start and costs and manual operations kept low.
A portal that scales without more operations work
- A fault-tolerant deployment foundation. That absorbs traffic spikes without manual intervention.
- Daily operational tasks. That were run by hand and needed to run reliably on a schedule.
- Frontend and backend. That had to be packaged as portable, consistent services.
- Secure, efficient traffic routing. With live visibility of performance.
- Manual deployment steps. That slowed the path from code to production.
What FiftyFive built
FiftyFive built and deployed the portal as an automated platform on Azure: Dockerfiles and Docker Compose configurations for the frontend and backend; multi-stage CI/CD pipelines in Azure DevOps; Kubernetes manifests for deployments, services and Ingress, with path-based routing; Helm-based provisioning of PostgreSQL, the Application Gateway Ingress Controller and cert-manager from within the Azure pipelines; scheduled automation for the daily operational jobs; real-time traffic monitoring on the application gateway.
How the solution works
From commit to container
- The frontend and backend are packaged as Docker images, so each environment runs the same artefacts.
- Azure DevOps multi-stage pipelines build and deploy them, replacing manual release steps.
Orchestration and routing
- Kubernetes runs the services from version-controlled manifests for deployments, services and Ingress.
- Ingress rules route requests by path to the right service.
- The Application Gateway Ingress Controller connects Kubernetes Ingress to the Azure application gateway, and cert-manager handles TLS certificates.
Provisioning with Helm
- PostgreSQL, the ingress controller and cert-manager are installed through Helm charts from within the Azure pipelines, so environments can be reproduced consistently.
Operations and monitoring
- Daily jobs that were run by hand now run on a schedule.
- Real-time traffic monitoring on the application gateway surfaces performance issues before they affect customers.
Technology stack
What the solution enabled
Business transformation
Less deployment time
Availability on Kubernetes and Azure
Lower operational overhead
70% less deployment time
Multi-stage pipelines replaced manual deployment steps.
99.9% availability
Kubernetes orchestration kept the portal stable through high-traffic periods.
40% lower operational overhead
Scheduled automation removed manual job handling.
A live portal handling real customer transactions
Built and deployed on Kubernetes on Azure.
FiftyFive Technologies designed, built and deployed a customer sales portal for a European aftermarket spare-parts company that needed to handle growing, spiky demand without adding manual operations work. FiftyFive containerised the frontend and backend with Docker, deployed them on Kubernetes on Azure through Azure DevOps multi-stage pipelines, provisioned PostgreSQL, the Application Gateway Ingress Controller and cert-manager with Helm, and automated daily jobs. Deployment time fell by 70%, availability reached 99.9% and operational overhead fell by 40%.
Technical questions
How are the frontend and backend packaged?
The frontend and backend are packaged as Docker images, so each environment runs the same artefacts. Azure DevOps multi-stage pipelines build and deploy them, replacing manual release steps.
How does Ingress route requests to the right service?
Ingress rules route requests by path to the right service. The Application Gateway Ingress Controller connects Kubernetes Ingress to the Azure application gateway, and cert-manager handles TLS certificates.