Skip to content
BritonOne Technology
Cloud & DevOpsAutomotive

Connected-vehicle platform for a carmaker

Built a cloud platform ingesting telemetry from 1.2M connected vehicles at scale.

1.2M
GCPKubernetesPub/SubBigQuery
Connected-vehicle platform for a carmaker
IndustryAutomotive
DisciplineCloud Platforms
CountryGermany
Headline result1.2M
The story

Problem, approach, and the outcome

About the client

The client is a German carmaker whose connected fleet (around 1.2 million vehicles) generates telemetry at a scale their existing platform could no longer absorb. Data volume grows with every vehicle sold, so the ceiling kept rising.

Multiple feature teams were each building their own ingestion plumbing, duplicating effort and diverging in quality and reliability.

The challenge

Vehicle telemetry had outgrown the existing platform, and volume was only heading one way as the connected fleet grew. The infrastructure was on the wrong side of a scaling curve.

Every feature team was rebuilding the same ingestion plumbing, duplicating effort and diverging in quality. The same problem was being solved repeatedly, badly, in parallel.

The carmaker needed a scalable foundation that let feature teams focus on features, not infrastructure. Freeing teams from undifferentiated plumbing was as much the goal as raw scale.

Our approach

We built a governed streaming platform with golden paths, so feature teams ship onto shared, scalable ingestion instead of rolling their own. Golden paths turn a repeated infrastructure problem into a solved one.

The platform elastically absorbs launch-day spikes, when telemetry surges as new models come online, and governance was baked in so shared use never became a shared liability. Consistency and safety came built into the paths teams use.

We migrated existing teams onto the golden paths incrementally, retiring the duplicated plumbing as we went. The consolidation happened without disrupting live telemetry.

Results
  • Telemetry from 1.2M vehicles ingested at scale
  • Golden paths for feature teams
  • Elastic to launch-day spikes
  • Duplicated per-team ingestion plumbing retired
Next step

Get a senior architect on the call, first time, every time.

No SDR gauntlet. 30 minutes with an engineer who can scope the problem, name the risks, and give you an honest feasibility call.