INTERACTIVEENGINEERING PLAYGROUND

Small experiments from backend systems, automation and deployment.

Explore → break things → see what happens.

EXPERIMENT 01/SIMULATED REQUEST

HTTP/1.1

API RESPONSE

See how different API outcomes behave.

GET/api/users/42

Status200 OK

Latency42ms

RequestGET

application/json

{
  "id": 42,
  "name": "Ayush",
  "role": "backend"
}

Deterministic mock responseno network call

EXPERIMENT 02/DATABASE ENGINE

EXPLAIN

QUERY PIPELINE

Step through how a relational database plans and executes queries.

Input Query

SELECT *

FROM users

WHERE active = true;

Execution Pipeline (click to inspect)6 stages

Stage 04: INDEX SCAN

Inspection panel

Traverses B-Tree index to locate row identifiers (TIDs) matching predicate.

Index used:users_active_idx

Rows scanned:128

Rows returned:24

Educational abstractionPostgreSQL planning model

EXPERIMENT 03/FAULT TOLERANCE

RETRY LOGIC

RETRY POLICY

Watch transient connection failure recover via exponential backoff.

REQUESTAPIDATABASE

Click SIMULATE FAILURE to observe retry mechanics.

Prevents cascading network outagesidempotent retry

EXPERIMENT 04/SIMULATION

deploy.sh

DEPLOYMENT PIPELINE

Simulate a zero-downtime production deployment with automated health checks.

$ ./deploy.shNon-destructive

Click RUN DEPLOYMENT to start the pipeline simulation.

Mocked bash deployment routinePM2 cluster target

EXPERIMENT 05/SIGNATURE LAB

SCENARIO 1 OF 5

HOW WOULD YOU DEBUG THIS?

Real backend problem solving. Choose the first move, inspect engineering reasoning, and discover core principles.

THE PROBLEMPRODUCTION 500

The API works perfectly on localhost. Production returns HTTP 500.

What do you check first?

Deterministic debugging heuristics

Built to experiment. Not to pretend.