Track & Trace Platform

C# .NET Angular Azure Terraform MediatR

Track & Trace Platform "TNT" — Planzer (Logistics, Switzerland)

Engineered a high-throughput microservice in .NET & Onion Architecture—went live with zero downtime handling 100 000+ API calls on day 1.

Show more ↓

1. Problem

Planzer processes tens of thousands of orders daily. Customers and depot staff need real-time shipment status, but the legacy Track & Trace system was slow, fragile and difficult to extend.

2. Solution Overview

I helped design and build TNT, a microservice that exposes reliable Track & Trace APIs and a responsive web UI.

Component Purpose Key Tech & Patterns
TNT API Idempotent read/write endpoints for order status ASP.NET Core · Onion Architecture · MediatR · EF Core
Email Service Event-driven status notifications Azure Service Bus · FluentEmail
Web App Angular SPA for internal & external users Angular · Tailwind
Infra Four isolated envs (dev / test / acpt / prod) Terraform · Azure DevOps

Security & Reliability: geo-redundant SQL & storage, automated integration tests in CI, feature-toggle cut-over from legacy to TNT.

3. Impact

  • 100 000+ API calls handled on launch day with 0 P1 incidents
  • Legacy system fully decommissioned via toggle after 24 h
  • Maintained 100 % availability during migration; no customer-visible bugs
  • Test coverage ≥ 85 % line; integration tests guard critical flows

4. My Contributions

Implemented core business logic & idempotent APIs, authored integration-test suite and EF Core migrations, designed the email notification module, drove adoption of Onion Architecture within team, presented sprint reviews to stakeholders—making complex topics easy to grasp.

5. Key Challenges & Mitigations

Challenge Mitigation & Result
High order volume spike at go-live Load-tested → tuned DB indices & caching → sustained 2 × expected TPS
Zero-downtime cut-over Feature toggles + blue/green deployment → instant switch with rollback safety
Ensuring idempotency Correlation keys & MediatR pipeline validation → duplicate requests drop to 0 %
Team ramp-up on Onion Architecture Pair-coding & knowledge sessions → consistent codebase, faster PRs