Tools — Systems lab

Backend failures, made visible.

Small interactive demos of the problems that show up in real payment systems: a webhook that returns 200 while the write fails, duplicate events, bad signatures, and silent database timeouts, plus retry storms and rate limiting. Everything runs in your browser.

Demos

Incident debugger

Payment succeeds, invoice missing

Case study

Step through the failure chain from gateway webhook to database timeout.

Start

Webhook received

Razorpay delivered the payment event and the endpoint returned HTTP 200.

API reliability probe

Check public endpoints

A lightweight reachability check for the domains already on this portfolio. Cross-origin responses are measured as reachable/failed, not inspected.

oakstat.us Idle
easybin.xyz Idle
lorm.pro Idle
uscs.sufi.my Idle
invoice.sufi.my Idle
plainly.sufi.my Idle

Webhook simulator

Choose a failure mode

Fintech
HTTP 200 Persist transaction, publish invoice event.

Idempotency key is new, signature is valid, and persistence succeeds.

Log trace explorer

Trace by transaction ID

12:04:11.018 waiting for trace...

Architecture snapshot

Payment flow boundaries

Click a node
request webhook write logs
System map

Every boundary can fail silently.

Click a node to see where things break in a real payment flow.

Spot the bug

Find the defect

A real-world code smell. Click the line you think is wrong, then read the explanation.

 
Pick a line to check.

Retry storm

Backoff and jitter vs thundering herd

200 clients hit a service that is down until t = 4 s. Compare how each retry strategy loads it when it recovers. Seeded, so every run is identical.

0 s

Result

Pick a strategy and press Run.

Rate limiter

Token bucket

Steady traffic of 6 requests/s. A request takes one token; with none left it gets HTTP 429. Hit Burst to see the bucket absorb a spike.

Tokens 10.0 Allowed 0 Rejected 429 0