Continental · automotive
A fleet tire service platform, modernised while it kept running
- 6 to 8 years on it, each of us
- New frontend platform since 2022
- Angular · Java · Spring Boot · Kubernetes
The system Continental’s tire service network uses to record work on commercial vehicle fleets, handle orders and invoicing, and track casings. A large Java platform with two decades of history, tied into the company’s ERP, and in daily use across the network.
- A new user interface. We designed and built the Angular frontend platform from scratch (shared component library, design system, Storybook, end-to-end tests) and have been moving the product onto it since 2022, screen by screen, with the system in use throughout.
- A database migration, data and all. The platform now runs on a different database engine, with its full history intact. We did the same again on the casing system below.
- A backend that stays supportable. Framework and runtime upgrades measured under production-like load before they go anywhere near production, and a REST API for the client’s external integrations.
- A test safety net that runs on every build. End-to-end, API and load tests, including load tests against a database seeded with millions of rows.
- Containerised and deployed on Kubernetes through automated release pipelines.




