$ ls /var/reports — 7 entries
Selected work, written the way I think about it on call: what broke or needed building, the constraint, the decision, and what I'd revisit.
Moving a live datastore from MongoDB to PostgreSQL without losing a row — the hard part was correctness during cutover, not the schema.
read the report →app
├─▶ mongo (old · read)
└─▶ postgres (new · dual-write)
│
reconcile ──▶ flip read ──▶ retire mongo
· rollback-safe at every step ·
One slow SMS provider could stall all of them. Lane isolation over a shared priority queue; a targeted cache cut analytic-store load 85–95%.
read the report →inbound ▶ ┌─────────────┐
│ dispatcher │
└──────┬──────┘
┌─────────┼─────────┐
▼ ▼ ▼
[lane A] [lane B] [lane C] topic·DLQ·retry
▼ ▼ ▼
provider A provider B provider C
(slow)
Scaling a team and product without scattering into premature microservices — ~80 bounded contexts in one deployable, each with an isolated queue.
read the report →┌──────── one deployable ─────────┐ │ [loyalty▸q] [payments▸q] │ │ [messaging▸q] [crm▸q] … ~80 │ │ bounded contexts · isolated q │ └─────────────────────────────────┘
The interesting part of multi-provider payments isn't the integrations — it's the idempotency that makes a double-spend impossible.
read the report →checkout / invoicing / settlement
│
[domain interface]
initiate · verify · settle
│
┌───────┴────────┐
│ idempotency │ ← double-spend guard
│ guard │
└───────┬────────┘
┌───────┴────────┐
[strategy A] [strategy B] …
(provider-specific · self-registering)
You can't cut what you can't see: attributing cluster spend per product line made a −30% reduction obvious.
read the report →prometheus metrics + workload labels
│
[attribution tool]
resource usage → product owner
│
grafana · per-team dashboards
│
teams own their footprint
→ optimizations follow
The upstream offered no API for per-user limits, so enforcement was derived from observed traffic instead — a log-parsing limiter that shipped.
read the report →┌────────── single K8s pod ──────────┐ │ nginx (traffic termination) │ │ │ │ │ xray (protocol handling) │ │ │ ↑ │ │ access logs ──▶ py-limiter │ │ (observed traffic → enforcement) │ │ supervisord (process health) │ └────────────────────────────────────┘
A loyalty platform is only as good as its reach — the integration had to land inside WooCommerce, not alongside it, and hook into the OTP auth merchants already run.
read the report →[Dobare platform API]
▲
│ REST · webhook
│
┌──────┴──────────────────┐
│ WooCommerce plugin │
│ REST controllers │
│ Gutenberg block │
│ OTP auth bridge │
└─────────────────────────┘
│
merchant storefront
(theme + plugins I don't control)