Why Deno Deploy enables edge computing - Challenge Your Understanding

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is a key feature of Deno Deploy that supports edge computing?

Which feature of Deno Deploy allows it to run code closer to users, reducing latency?

A It runs code on centralized cloud servers only.

B It requires manual server setup for each region.

C It only supports running code on local machines.

D It deploys code to multiple global edge locations automatically.

💡 Hint

Think about how edge computing reduces delay by running code near users.

Deno Deploy automatically distributes your code to many edge locations worldwide, so requests are handled close to users, reducing latency.

❓ component_behavior

intermediate

How does Deno Deploy handle incoming requests to enable edge computing?

When a user sends a request, how does Deno Deploy process it to ensure low latency?

A It routes the request to the nearest edge server running your code.

B It forwards the request to a central server regardless of user location.

C It queues the request until a server is manually assigned.

D It processes the request only after downloading the entire app.

💡 Hint

Consider how edge servers reduce travel time for data.

Deno Deploy routes requests to the closest edge server, so your code runs near the user, lowering response time.

❓ lifecycle

advanced

What happens when you update your code in Deno Deploy regarding edge computing?

After deploying a new version of your code, how does Deno Deploy ensure the update is available globally at the edge?

A It updates only one central server and waits for manual replication.

B It instantly pushes the update to all edge locations worldwide.

C It requires you to redeploy separately to each edge location.

D It delays updates until all users disconnect.

💡 Hint

Think about how edge computing platforms keep code consistent everywhere.

Deno Deploy automatically and instantly distributes your updated code to all edge servers, ensuring users everywhere get the latest version.

📝 Syntax

advanced

Which Deno Deploy code snippet correctly handles an HTTP request at the edge?

Select the code snippet that properly responds to an HTTP request in Deno Deploy's edge environment.

A addEventListener('fetch', event => { event.respondWith(new Response('Hello from edge!')) })

B onRequest((req) => { return new Response('Hello from edge!') })

C fetch('request', (event) => { event.respondWith('Hello from edge!') })

D serveHttp((req) => new Response('Hello from edge!'))

💡 Hint

Look for the standard event listener pattern for fetch events in Deno Deploy.

Deno Deploy uses the 'fetch' event listener to handle HTTP requests at the edge. Option A correctly uses addEventListener with event.respondWith.

🔧 Debug

expert

Why does this Deno Deploy edge function fail to respond correctly?

Given this code snippet, why does the function not send a response to the user? ```js addEventListener('fetch', event => { new Response('Hello from edge!') }) ```

Deno

addEventListener('fetch', event => {
  new Response('Hello from edge!')
})

A The function is missing an async keyword to handle the response.

B The event listener should be named 'request' instead of 'fetch'.

C The response is created but not passed to event.respondWith, so no response is sent.

D The Response constructor is used incorrectly; it needs a second argument.

💡 Hint

Check how the response is linked to the event to send it back.

In Deno Deploy, you must call event.respondWith() with the Response object to send it. Just creating a Response does nothing.

Practice

1. What is the main benefit of Deno Deploy running code near users in edge computing?

easy

A. It increases the size of the app's codebase.

B. It reduces the delay or latency for users accessing the app.

C. It requires users to install special software.

D. It makes the app run only on one central server.

Solution

1. Step 1: Understand edge computing basics

   Edge computing means running code close to users to reduce the time data travels.

2. Step 2: Connect Deno Deploy's role

   Deno Deploy runs code on many servers worldwide, so users get faster responses.

3. Final Answer:

   It reduces the delay or latency for users accessing the app. -> Option B

4. Quick Check:

   Edge computing = less delay = B [OK]

Hint: Edge computing means less delay by running code near users [OK]

Common Mistakes:

• Thinking edge computing increases app size
• Believing users need special software
• Assuming code runs only on one server

2. Which of the following is the correct way to deploy a simple Deno script to Deno Deploy?

easy

A. deno install main.ts

B. deno run main.ts

C. deno deploy --project=myapp main.ts

D. deno build main.ts

Solution

1. Step 1: Identify Deno Deploy command

   The command to deploy code to Deno Deploy is 'deno deploy' with project and file.

2. Step 2: Check other commands

   'deno run' runs locally, 'deno install' installs scripts, 'deno build' is not a Deno command.

3. Final Answer:

   deno deploy --project=myapp main.ts -> Option C

4. Quick Check:

   Deploy command starts with 'deno deploy' [OK]

Hint: Use 'deno deploy' to send code to Deno Deploy service [OK]

Common Mistakes:

• Using 'deno run' to deploy code
• Confusing install with deploy
• Trying 'deno build' which doesn't exist

3. Consider this Deno Deploy code snippet:

addEventListener('fetch', event => {
  event.respondWith(new Response('Hello from edge!'))
})

What will a user see when accessing this deployed script?

medium

A. The text 'Hello from edge!' displayed in the browser.

B. An error message about missing fetch handler.

C. A blank page with no content.

D. A JSON object with server details.

Solution

1. Step 1: Understand the fetch event listener

   The code listens for fetch requests and responds with 'Hello from edge!'.

2. Step 2: Determine the response content

   The response is a simple text string sent back to the user.

3. Final Answer:

   The text 'Hello from edge!' displayed in the browser. -> Option A

4. Quick Check:

   fetch event returns 'Hello from edge!' [OK]

Hint: fetch event responds with given text string [OK]

Common Mistakes:

• Expecting JSON instead of plain text
• Thinking no response is sent
• Confusing event listener with error

4. This Deno Deploy code throws an error when deployed:

addEventListener('fetch', event => {
  event.respondWith('Hello from edge!')
})

What is the error and how to fix it?

medium

A. Error: respondWith expects a Response object, fix by wrapping string in Response().

B. Error: fetch event missing, fix by adding fetch event listener.

C. Error: Syntax error, fix by adding semicolon after respondWith.

D. No error, code works fine as is.

Solution

1. Step 1: Identify respondWith argument type

   respondWith requires a Response object, not a plain string.

2. Step 2: Fix by wrapping string in Response()

   Use event.respondWith(new Response('Hello from edge!')) to fix error.

3. Final Answer:

   Error: respondWith expects a Response object, fix by wrapping string in Response(). -> Option A

4. Quick Check:

   respondWith needs Response object [OK]

Hint: respondWith must get Response object, not plain string [OK]

Common Mistakes:

• Passing string directly to respondWith
• Missing fetch event listener
• Assuming semicolon fixes error

5. You want to build a fast app using Deno Deploy that serves personalized greetings based on user location. Which feature of Deno Deploy best supports this edge computing use case?

hard

A. Requiring users to download the entire app before use.

B. Using global caching only without running code near users.

C. Running code on a single central server to simplify logic.

D. Running code on many servers worldwide close to users to reduce latency.

Solution

1. Step 1: Understand personalized greetings need low delay

   Personalized greetings require quick response based on user location.

2. Step 2: Identify Deno Deploy's edge computing feature

   Deno Deploy runs code on many servers worldwide near users to reduce delay.

3. Step 3: Compare options

   Only running code near users (Running code on many servers worldwide close to users to reduce latency.) supports fast personalized responses.

4. Final Answer:

   Running code on many servers worldwide close to users to reduce latency. -> Option D

5. Quick Check:

   Edge computing = code near users = A [OK]

Hint: Edge computing means code runs near users for speed [OK]

Common Mistakes:

• Thinking central server is faster
• Confusing caching with code execution
• Believing users must download app fully