Automotive · Asset management

Australian vehicle auction company: Next.js case study

Full-stack work on an asset-management platform for an Australian vehicle auction company: CQRS microservices, GraphQL and Kafka on Azure, with a Next.js app for the screens.

Tech Stack:Next.jsMicroservicesCQRSGraphQLKafkaMSSQLAzure

The Problem

A vehicle auction business moves a constant flow of vehicles and other assets through intake, listing and sale. The company needed an asset-management platform that several teams could build on at once without stepping on each other, and that kept every change to an asset traceable.

The Solution

Apex36 worked full stack inside a ten-person delivery team (six developers, two QA engineers, a business analyst and a scrum master) from December 2023 to November 2024. We built asset-management features end to end: backend microservices on the CQRS pattern, with commands and queries split so reads stay fast while writes are validated, GraphQL APIs over MSSQL, Kafka events between services, and the matching screens in the Next.js app. Work was planned and split at feature level with the other developers. The platform is live in production.

Features

Asset-management features

Features for managing vehicles and other assets on their way through the auction process.

CQRS microservices

Commands and queries split into separate paths, so writes are validated and reads stay fast.

GraphQL and Kafka

GraphQL APIs over MSSQL, with Kafka events carrying changes between services.

Next.js app screens

The screens that sit on top of those services, built in the platform's Next.js app.

Results / Impact

Live in production

on Azure.

Eleven months

December 2023 to November 2024, inside a ten-person delivery team.

FAQ

Asset-management features end to end: CQRS microservices, GraphQL APIs, Kafka events and the matching screens in the Next.js app. We worked in a ten-person team, with features split between the developers.

Auction data is read far more often than it is changed, and every change needs checks. CQRS separates the two, so the read side can be shaped for fast screens while the write side validates every change to an asset.

Yes. This is how staff augmentation and dedicated teams work with us: our engineers join your sprints, tools and code reviews, and you keep the code.

Ready to build something impactful?

Let's discuss your project and how we can help you ship faster and smarter.

Book a Free Strategy Call