Builder Academy · Learning pathway

Engineering connected systems

Explore how software, data, research, security and operations fit together. Start with the mental model, try a synthetic exercise, then apply it to a portfolio project.

Three visual starting points

Make the invisible parts easier to understand.

Explore requests, retries and access decisions through interactive examples.

Delivery timeline

  1. 1 / Upcoming

    First attempt fails

    No business action was performed.

  2. 2 / Upcoming

    Wait before retrying

    Backoff avoids immediately repeating a failed request.

  3. 3 / Upcoming

    Retry succeeds

    Event demo-001 is processed once.

  4. 4 / Upcoming

    Duplicate is skipped

    The event ID prevents repeating the business action.

01 / Webhook delivery

One event. Several destinations.

A source reports a change. Follow one fictional receiver through a failed delivery, a retry, and the same event arriving again.

Local simulation · event demo-001 · no network calls

Ready. No requests have been made. Follow the middle receiver in the illustration.

Attempts
0
Business actions
0
Duplicates skipped
0
  1. Send the event to the intended endpoint.
  2. If delivery fails, wait before a limited retry.
  3. Use an event ID to avoid doing the same work twice.

An acknowledgment confirms receipt, not that every downstream task finished. Retries can still fail and need review.

Follow a request through an app →
  1. 1. API

    Receives and validates a request, then queues a job.

  2. 2. Worker

    Picks up the queued job and performs the background work.

  3. 3. Database

    Stores the result so the application can retrieve it.

02 / Infrastructure

Give each part a clear job.

An API receives requests, a worker handles background jobs, and a database stores records. These roles can share infrastructure or run separately.

One possible background-job flow, not a required architecture. These roles do not each need a separate physical server.

03 / Access checks

Identity first. Permission next.

Authentication checks who is making a request. Authorization checks whether that identity can perform this action on this record.

Try a fictional access check

Request to edit a record

1. Is the requester signed in?

No → 401

Sign in first.

Selected outcome

Yes → check permission

2. Can they edit this record?

No → 403

Permission required.

Yes → 200

Sample edit allowed.

401 · Sign in first

The server cannot establish an authenticated identity. In this example, the request is rejected before the record can be edited.

Compare the example responses. Reloading resets your choices.

Explore programming foundations →

This diagram explains a decision; the application must enforce both checks on the server.

Capstone: research you can trust

Use public or synthetic cybersecurity sources to map source → capture → hash → entity → claim → review → downstream product. Never confuse a provider result with independently verified evidence.

Start with the Account Signal Engine Research Hub and its RSS / Firecrawl foundation; add paid providers only after security, cost and quality evaluation.