Faculty planning guide · 5 min read

How to plan a CDN guest lecture

A content delivery network (CDN) session works best when students tackle one delivery decision, rather than tour every feature. Start with syllabus fit.

Need a streaming expert for a class?

I bring production streaming experience into university classrooms. Ask about a CDN session tailored to your networking course.

Choose the decision students should make

A CDN guest lecture can connect networking theory to decisions about origin load, cache freshness, and delivery failures. Choose one question your course already raises.

For an introductory class, ask students to trace a request through a client, an edge cache, and an origin server. For advanced students, add a policy decision: which responses should a shared cache reuse, and when should it contact the origin?

Keep transport comparisons and vendor demonstrations outside the core scope unless they directly serve that objective. This guide focuses on planning and assessment, not choosing among networking topics.

Check prerequisites before choosing the depth

Students should recognize a Hypertext Transfer Protocol (HTTP) request and response, understand the Domain Name System (DNS), and distinguish latency from throughput. Familiarity with caching helps.

If students have not covered those concepts, schedule a short faculty-led recap before the visit. No CDN account or programming exercise is necessary for a diagram-based discussion.

For a header-level exercise, check that students can read response headers and understand shared versus private caches. Share the terminology used in your course beforehand.

Write three assessable learning objectives

Use these proposed objectives as a starting point, then adjust them to the students' level. Each should produce an explanation or decision you can assess.

  • Trace a cache hit and a cache miss, identifying when the origin receives a request.
  • Explain how freshness and validation influence reuse, origin load, and the risk of serving outdated content.
  • Defend a caching policy for a stated scenario, including what must not be shared between users.

Use a proposed 90 min session outline

The following is a planning proposal, not Mathias Guille's lecture deck, a delivered curriculum, or a confirmed session. Agree the actual agenda together.

Use a hypothetical university video service as the common case. Separate a public video segment from a personalized account response, without using real student data.

  • 0–10 min: establish the scenario, assumptions, and learning objectives; check the prerequisite vocabulary.
  • 10–25 min: trace the public segment request through client, edge, and origin; compare cache hits and misses.
  • 25–45 min: discuss freshness and validation, then contrast public content with a personalized response that needs explicit privacy controls.
  • 45–65 min: small groups propose a policy for a traffic surge; state assumptions about freshness, capacity, and content sensitivity.
  • 65–80 min: compare decisions and reserve questions for the practitioner, including what evidence would change a recommendation.
  • 80–90 min: use an exit question to check understanding and connect the discussion to the next course topic.

Prepare one small exercise, not a lab platform

Give students a diagram and two hypothetical responses: a public video segment and an account page. Ask what may be reused across users, and why.

Set the constraints explicitly: acceptable staleness, whether the content changes, and whether it contains personal data. Students should explain their reasoning before suggesting headers.

HTTP caching rules distinguish no-cache, which requires validation before reuse, from no-store, which prohibits storage. Use RFC 9111 to verify any header examples.

An exit question might ask: 'A cached segment is stale; what additional information determines whether the cache can serve it?' Assess assumptions, not a memorized slogan.

Faculty preparation checklist

Before confirming a session, prepare a short brief. It should make clear what students already know and what this visit adds to your teaching.

  • Share the course description, student level, cohort size, and concepts covered before the proposed visit.
  • Choose one delivery case, three objectives, and topics to exclude; use public or hypothetical examples only.
  • Specify a 60–90 min slot and protect discussion time. For 60 min, simplify the exercise rather than compress every section.
  • Discuss English or French, remote or in-person delivery, time zone, accessibility needs, and room or video arrangements.
  • Agree any demonstration requirements and a static fallback. Confirm recording and material-sharing permissions rather than assuming permission.
  • Choose the exit question and decide how to revisit it in the next class. Discuss fees and arrangements privately before confirming.

Ask Mathias about your course fit

I tailor guest lectures after a short conversation with the professor. Send your course context and priority learning objective to ask whether CDN and edge fits.

You do not need a finished agenda to inquire. The form selects CDN & Edge Delivery; include prerequisites or open questions in the course message.

StreamWise's site and business are built and run by AI agents on NanoCorp; Mathias leads the lectures.