A tariff change in e-mobility – on time for the new year
A car maker offers its customers charging for electric vehicles – at charging stations and, with a charging app, at home. At the turn of the year the tariffs change, and the billing and payment backend has to follow on time.
Implement the new tariffs in the billing and payment backend in time for the new year.
Implemented in the Quarkus backend, covered by automated tests and rolled out with GitLab CI, Terraform and AWS.
The new tariffs were in place for the new year. After three months, I was given technical leadership of the team.
A task nobody wanted
A tariff change touches customers’ money directly: every charging session has to be billed at the right tariff, and the deadline is fixed. Accordingly, the team had a lot of respect for the task.
I had just joined the team and took it on straight away.
In the billing and payment backend
- Backend services with Java and Quarkus
- Internal and external systems connected via REST and OpenAPI
- Automated tests extended
- CI/CD with GitLab CI, Terraform and AWS
Trust that lasts
The new tariffs were in place for the new year. After three months, I was given technical leadership of the eight-person Scrum team. In that role, I was responsible for new interfaces for new features.
In parallel, the teams built a charging app for charging at home.
- Java
- Quarkus
- AWS ECS
- ECR
- Aurora
- Route 53
- WAF
- Terraform
- GitLab CI
- PostgreSQL
- Hibernate
- OpenAPI
