SkillsTech RoomsSkillsTech Rooms™
Create room
← All rooms
System DesignLiveRoom only

System Design: settlement at 10x scale

Defend a redesign of the settlement pipeline for 10x volume.

acme/payments-svcScheduled Fri, Jul 3, 5:30 PM (4d ago)3 participants
Join live room

Agenda

2/4 done · 35 min planned

  1. ✓

    Frame constraints & non-goals

    5m
  2. ✓

    Walk current settlement flow

    8m
  3. 3

    Propose redesign & defend tradeoffs

    15m
  4. 4

    Failure modes & rollout

    7m

Artifacts

Artifact-aware: this room is about real work, not an empty call.

  • OTOpenThunderRoom only

    payments-svc - Architecture & Risk Report

    OpenThunder mapped 3 hotspot modules, 2 high-risk change areas, and the settlement flow. Risk score 68/100.

    architecture_report · from OpenThunder

  • IDESkillsTech IDERoom only

    acme/payments-svc @ main

    Live repo opened from SkillsTech IDE. 41k LOC, TypeScript + Postgres.

    repo · from SkillsTech IDE

  • STTSkills Tech TalkPrivate

    Architecture Defense - STT Drill

    Skills Tech Talk drill on explaining tradeoffs under pressure. Communication baseline 3.4/5.

    stt_drill · from Skills Tech Talk

Notes

Decisions, risks, strengths, and action items

  • Decision

    Split settlement into an idempotent ingress queue + async reconciler.

    Fri, Jul 3, 5:42 PM

  • Risk

    Dedupe key collision under retry storms - needs a stronger key.

    Fri, Jul 3, 5:48 PM

  • Strength

    Clear articulation of the consistency/latency tradeoff.

    Fri, Jul 3, 5:54 PM

Where this room came from

Provenance carried from the product that started it.

OTOpenThunder

Started from OpenThunder · on Cloud

Repo session

Repo
acme/payments-svc
Access
Authorized upstream
Report
art_ot_payments

A room never widens repo access; it inherits what was already authorized.

Return to OpenThunder →

Participants

3 in this room

  • AO

    Amina Okafor◆ 91

    Interviewer · @amina

  • Y

    You◆ 78

    Candidate · @you

  • DK

    Dana Kim◆ 95

    Observer · @danak

Rubric · Architecture Defense

From Skills Tech Talk · scores communication & explanation · not yet scored

  • Problem framing

    -

    States constraints, scale, and non-goals before designing.

  • Tradeoff reasoning

    -

    Compares options and defends the choice out loud.

  • Failure modes

    -

    Names what breaks and how the design degrades.

  • Communication clarity

    -

    Explains complex ideas an interviewer/exec can follow.