The problem wasn’t that the features didn’t work — it was that our demo environment didn’t reflect how real systems behave. Enterprise customers care about dependency graphs, runtime debugging, and governance signals under real traffic. A single-service demo simply didn’t hold up in senior engineering conversations.
The timeline constraint shaped the entire architecture. This wasn’t an open-ended infrastructure project. We needed something credible, reproducible, and easy to reset — fast. That forced disciplined trade-offs.
Notice these goals balance product storytelling with operational reliability. It wasn’t just about technical correctness — it was about field usability.
Each service runs in its own namespace to preserve clean boundaries. Ingress routes traffic via path-based rules. The Insights Agent runs cluster-wide as a DaemonSet for operational parity with production observability patterns.
3 Repositories:
accounts-api handles:
We considered a fourth “platform” repository but rejected it to reduce onboarding friction. Three repos with one orchestrator struck the right balance.
Problem:
Solution:
Trade-off:
This was a pragmatic Kubernetes constraint. Rather than flatten namespaces, we added minimal indirection to keep boundaries intact.
Implemented:
Impact:
In demo infrastructure, reset speed matters more than optimization. If something breaks mid-demo, the ability to recover quickly is critical.
Traffic generator:
Output:
A dashboard showing only green signals lacks credibility. Injecting controlled failure makes the observability story tangible.
Chose Kind over Cloud because:
Trade-off:
Under a one-week build window, velocity mattered more than infrastructure purity. We consciously sequenced realism later.
Enabled discussions around:
The real success metric wasn’t “does it run?” It was “does it elevate the technical depth of customer conversations?”
Two-tier model:
Local Tier (Kind)
Cloud Tier (AWS via Terraform / Pulumi)
The local tier solves enablement. The cloud tier unlocks enterprise realism. This phased strategy preserves speed while enabling scale.
This project demonstrates:
The goal wasn’t to build a demo. It was to build a platform for credible conversations.
The core contribution wasn’t any single script or manifest. It was the architecture and sequencing decisions that made this sustainable, reproducible, and aligned with the business.