The Runtime Theory
hard · 4h · 14 steps

Web Development Advanced

Real-time communication (WebSockets/SSE), SPA vs MPA architecture, security, and performance optimization at scale.

Curriculum (14 steps)

1

Client-side state with React/useState, server state with sessions and JWT, cookies vs localStorage, and caching strategies.

Start→
2

Resource-oriented design, HTTP methods and status codes, idempotism, versioning, pagination, and error response patterns.

Start→
3

How to push real-time updates from server to browser: polling, long polling, SSE, and WebSockets — with tradeoffs and use cases.

Start→
4

Single-page apps vs multi-page apps — tradeoffs in bundle size, SEO, time-to-interactive, and development complexity.

Start→
5

An event loop repeatedly selects ready work and runs callbacks or tasks.

Start→
6

Follow the key state changes and boundary checks involved in async code still runs on an event loop.

Start→
7

An interactive concept flow for async code still runs on an event loop, from its assumptions through the main operation and boundary checks.

Start→
8

A retry repeats work after the caller cannot determine whether an earlier attempt completed.

Start→
9

Threat-model a request by tracing sensitive data, user authority, trust boundaries, and the controls that limit abuse.

Start→
10

Follow a login attempt through rate limits, password-hash verification, authorization context, and a protected session cookie.

Start→
11

Follow request limits, account lookup, password verification, session rotation, and later authorization checks.

Start→
12

A security prompt about password verifiers, salts, offline guessing, authentication, session creation, and authorization.

Start→
13

A cache stores reusable results near the request path to reduce repeated work or latency.

Start→
14

An interactive concept flow for caching and routing change the request path, from its assumptions through the main operation and boundary checks.

Start→