Skip to content

Home

Jump to bottom
Terrence Daniels edited this page Sep 11, 2026 · 14 revisions

A self-contained, event-driven platform simulating a utility company's meter-reading, usage-aggregation, and billing pipeline. An original design — not a fork or a cloned reference app — built to demonstrate the skills a Principal Developer role expects: distributed systems design, microservices decomposition, event streaming, resilient service-to-service communication, CI/CD, and production-grade observability.

This wiki is a set of short pointers, not a duplicate of the real documentation — each page states one thing worth knowing and links to the authoritative source rather than repeating it. For the full picture, start with README.md and the design document in the main repo.

Status: just started. Repo scaffolding is in place — README, MIT license, .gitignore, and the full design document (converted from the original PDF to HTML) — but no service code exists yet. Phase 1 (a direct-REST core loop: Meter Simulator → Usage Aggregation → Billing, single Postgres database) is next. See the Build Phases checklist in the README for the current phase-by-phase plan.

Foundation

  • Design Document — architecture rationale, service breakdown, Kafka event contracts, cross-cutting concerns (resiliency, idempotency, tracing, security, testing), CI/CD pipeline plan, and interview talking points
  • Build Phases — the 6-phase build order this project is actually following, tracked in the README until there's enough surface area to warrant a dedicated tracking doc

Services

Not built yet — service pages will show up here one at a time as each one lands, starting with the Meter Simulator, Usage Aggregation, and Billing services in Phase 1.

Elsewhere

Clone this wiki locally