Skip to content
All case studies

Smart City IoT Platform

Senior Backend Engineer 2024–2025

Five city domains were under development at once. I turned the programme’s specifications into service boundaries and API contracts that several vendor teams could build against in parallel.

Kubernetes services
20+
City domains
5
Delivery
API contracts and C4 models

The device telemetry path

  1. Device gateways

    Bring smart-city device events into the platform.

  2. Kafka

    Stream telemetry separately from general application data.

  3. Cassandra

    Store time-series readings for use by the city services.

Contracts between vendor teams

Five city domains were being built at the same time. I translated an external consultancy's specifications into C4 models and split the backend into bounded contexts, each with its own database and API. Those contracts let the vendor teams build in parallel, with the C4 models as their shared reference.

The service boundaries followed that delivery constraint. Device telemetry had a separate path through Kafka into Cassandra; PostgreSQL handled the general application data. APISIX and Keycloak provided the gateway and identity layer across the services.

What I delivered

In six months I designed and built 20+ microservices, including the shared user, onboarding, notification, certification and mail services in NestJS. I also built domain services such as smart parking and smart lighting. The delivery included the API contracts and reference models the other teams built against, with GitLab CI and monitoring through Grafana and Prometheus.

Services and architecture

Project Overview

Backend engineer on a smart-city programme. Five city domains were being built by several vendor teams at once, so the architecture had to give every team a bounded context with a clean API contract and a reference model they could build against, without waiting on each other.

Architecture

  • 20+ microservices on Kubernetes, each with its own database and API
  • APISIX as the API gateway, Keycloak for identity, GitLab CI for delivery
  • Kafka event streaming from the IoT gateways, Cassandra for time-series sensor data, PostgreSQL and Grafana alongside
  • Domain-driven design with clean contracts so several vendor teams could build in parallel

What I Built

  • The platform services the city domains ran on: user, onboarding, notification, certification and mail, in NestJS and TypeScript
  • Domain services such as smart parking, smart lighting, dashboard, marketplace and support
  • C4 architecture models translated from an external consultancy's specifications, which became the reference the vendor teams built against
  • Delivered in six months

Technical Stack

TypeScript NestJS Node.js Kubernetes Cassandra Kafka PostgreSQL APISIX Keycloak Grafana Prometheus GitLab CI Terraform Docker