Cloudflare Workers lets you run JavaScript on Cloudflare's network without managing a server yourself. You can use a Worker to receive a support form, return data to a website, or check access to a file. In this course, you will build these small, useful pieces and learn how to tell whether they work. Start by preparing your own learning account and connecting a LabEx terminal, then write, test, deploy and clean up your applications.
Required before starting
Before starting the first lab or launching its VM, read Prepare Your Cloudflare Learning Account and complete the account preparation in your browser. This required preparation does not need a LabEx VM. Continue only when your login email is verified, you can select your own dedicated learning account, Workers Free is its current plan, and you can open Workers & Pages in that account. Keep the account name handy;
LabEx Learningis a suggested display name. If your account is already prepared, read the guide and confirm these checkpoints before continuing.
The course contains eleven guided labs and a final configuration-repair challenge (12 labs); account preparation is required reading outside the course lab list. Practical scenarios include a support request API, an internal catalog service and a help center with static assets. Later labs introduce caching, scheduled health checks, release recovery and failure diagnosis. Each lab starts independently, so you carry forward your knowledge and learning account rather than relying on an earlier lab's VM or deployed resources.
What You Will Learn
- Prepare a Cloudflare learning account, authorize Wrangler from LabEx and confirm the intended account before deploying
- Develop JavaScript request handlers and deploy a Worker to a
workers.devaddress - Build API routes with method checks, JSON validation, upstream requests and useful error responses
- Separate environment configuration from secrets and test protected endpoints
- Test success and failure paths locally and repair a reproducible regression
- Connect a public Worker to an internal service through a service binding
- Serve a static help center alongside API routes and a protected resource
- Cache eligible public responses while excluding private data and errors
- Use
waitUntilfor bounded background work and observe a real Cron-triggered health check - Compare versions with deployments and restore a known-good release
- Diagnose upstream failures using request IDs, HTTP responses, logs and metrics
- Remove disposable cloud resources and disconnect the lab environment
Who This Course Is For
This course is for developers beginning with Cloudflare Workers who want practical experience building and troubleshooting small cloud applications. It also suits learners who know basic JavaScript and want to understand how code, configuration and deployed behavior fit together.
Prerequisites: You should be comfortable navigating a terminal and reading basic JavaScript functions, objects and modules. The labs explain the HTTP behavior, asynchronous work and platform concepts needed for each task. No previous Cloudflare Workers experience is required.
Learning environment: Prepare your account in a browser before launching a VM. All 12 course labs use independent LabEx Linux environments with their own setup and verification. Node.js and Wrangler versions are pinned. Use your browser for Cloudflare login, device authorization and Dashboard checkpoints. No purchased domain is needed; public endpoints use workers.dev.
Frequently Asked Questions
How is the course organized?
The preparation guide and eleven guided labs explain the work step by step. The final challenge asks you to repair preview configuration and maintenance-route authorization independently, then leave a clean workspace. Its complete solution is provided separately from the task requirements.
Will I use a shared Cloudflare account?
No. You use your own account and confirm its identity before making changes. The preparation guide explains how to establish a dedicated learning account. Each VM that needs cloud access receives its own authorization through the browser device flow.
Do the labs create real cloud resources?
Deployment labs create uniquely named disposable Workers in your learning account and use synthetic data. Their cleanup steps remove only those lab resources, confirm removal while still authorized and then log out. Local testing and the final challenge also provide practice that does not require a deployment.
Should I take the labs in order?
The listed order is recommended: prepare, connect, build, test, operate and diagnose. Later explanations reuse concepts introduced earlier, but each lab supplies a fresh workspace and creates its own required resources.
Do I need to submit screenshots?
No. Screenshots help you recognize Dashboard controls and expected page states. Executable labs assess the relevant behavior and resource state; the browser-only preparation guide provides explicit manual checkpoints.
Does this course cover databases or durable job processing?
This course focuses on Workers fundamentals. Background work and Cron examples use small, bounded health checks; they do not promise durable delivery or automatic retries. Storage services, queues and workflows are topics for later courses in the Cloudflare learning path.
