Edge Computing with Cloudflare Workers & Deno · Lesson

Shared Logic & Utilities

Implement shared utility functions and business logic that can be reused across Deno and Worker environments.

Shared Logic & Utilities is a free Edge Computing with Cloudflare Workers & Deno lesson on CoddyKit — lesson 3 of 4. You can read the complete lesson below for free — then practise it hands-on in the browser with a built-in code editor and a 24/7 AI tutor. It is part of the Edge Computing with Cloudflare Workers & Deno learning path, one of 4 lessons in the course, and your progress syncs across the web and the CoddyKit app.

Introduction to Shared Logic

When building applications for both Deno and Cloudflare Workers, you often encounter code that performs similar tasks. This is where shared logic comes in handy!

Shared logic refers to writing common functions or modules once and reusing them across different parts of your application, regardless of the runtime environment.

Why Share Code?

Reusing code between Deno and Worker environments offers several key benefits:

Consistency: Ensures the same behavior and calculations everywhere.
Maintainability: Updates to logic only need to be made in one place.
Reduced Duplication: Avoids writing the same code multiple times, saving effort.
Faster Development: Leverage existing functions instead of starting from scratch.

What Can Be Shared?

Many types of code are perfect candidates for sharing:

Utility Functions: String formatting, date manipulation, mathematical helpers.
Data Validation: Ensuring input data meets specific criteria.
Business Logic: Core application rules or calculations.
Type Definitions: TypeScript interfaces or types for consistent data structures.

The best candidates are usually pure functions that don't rely heavily on environment-specific globals.

Deno's ES Module System

Deno embraces standard JavaScript ES Modules (ECMAScript Modules) with a URL-based import system. This means you can import modules using relative paths (e.g., ./myModule.ts) or full URLs.

This adherence to web standards is crucial because Cloudflare Workers also primarily use ES Modules, making Deno modules naturally compatible.

Developing a Core Utility

Let's create a simple utility function. We'll define a function formatGreeting that takes a name and returns a personalized greeting. This function is pure and doesn't rely on any Deno or Worker-specific APIs.

Imagine this code lives in a file like sharedUtils.ts.

export function formatGreeting(name: string): string {
  return `Hello, ${name}! Welcome to the Edge.`;
}

Running the Utility in Deno

Here's how you would use our formatGreeting utility within a Deno application. In a real project, you'd import it from ./sharedUtils.ts, but for this runnable example, we'll include it directly.

// This code would typically import from a shared file.
// For runnable demo, function is inline.

function formatGreeting(name: string): string {
  return `Hello, ${name}! Welcome from Deno.`;
}

// Use the shared utility
const userName = "Deno User";
console.log(formatGreeting(userName));

Workers & Shared Modules

Cloudflare Workers execute JavaScript and TypeScript at the edge. They support ES Modules, just like Deno.

This means a .ts or .js file containing shared utility functions can often be directly imported and used in your Worker code, assuming it doesn't contain Deno-specific runtime APIs.

Running the Utility in a Worker

Now, let's see our formatGreeting utility used inside a Cloudflare Worker. The Worker will respond with the formatted greeting, potentially using a name from the URL query parameters.

// This code would typically import from a shared file.
// For runnable demo, function is inline.

function formatGreeting(name: string): string {
  return `Hello, ${name}! Welcome from the Worker.`;
}

export default {
  async fetch(request: Request): Promise<Response> {
    const url = new URL(request.url);
    const name = url.searchParams.get('name') || 'Guest';

    // Use the shared utility
    return new Response(formatGreeting(name), {
      headers: { 'content-type': 'text/plain' },
    });
  },
};

Handling Environment Differences

While many utilities can be shared directly, some logic might need to adapt to its environment.

Environment Variables: Deno uses Deno.env.get(), Workers use the env object passed to fetch.
File System Access: Available in Deno, not directly in Workers.
Global Objects: Be mindful of differences in global APIs (though fetch is now widely available).

Use abstraction layers or conditional logic (e.g., if (typeof Deno !== 'undefined')) to manage these differences gracefully.

Check Your Understanding

Which of the following are primary benefits of implementing shared logic between Deno and Cloudflare Worker environments?

Recap & Next Steps

Great job! In this lesson, we explored how to create and manage shared utility functions and business logic that can be reused across both Deno and Cloudflare Worker environments.

We understood the benefits of code sharing, like consistency and maintainability.
We saw how ES Modules enable seamless integration.
We demonstrated a simple utility running in both Deno and a Cloudflare Worker.
We discussed strategies for handling environment-specific differences.

This approach is key to building robust and efficient edge applications!

Frequently asked questions

Is the “Shared Logic & Utilities” lesson free?

Yes — the full text of “Shared Logic & Utilities” is free to read here on the web, and the Edge Computing with Cloudflare Workers & Deno course includes 4 lessons in total. To practise it interactively (a built-in code editor and a 24/7 AI tutor) and unlock the rest of the Edge Computing with Cloudflare Workers & Deno course, upgrade to CoddyKit PRO.

What will I learn in “Shared Logic & Utilities”?

Implement shared utility functions and business logic that can be reused across Deno and Worker environments. You practise Edge Computing with Cloudflare Workers & Deno with hands-on code you run directly in the browser, and a 24/7 AI tutor answers your questions as you work through the lesson.

Do I need any experience to start Edge Computing with Cloudflare Workers & Deno?

No prior experience is required. Edge Computing with Cloudflare Workers & Deno on CoddyKit is structured for beginners through advanced learners; this is — lesson 3 of 4, so you can start here or from the beginning and move at your own pace.

How long does the “Shared Logic & Utilities” lesson take?

Most CoddyKit lessons take about 5–10 minutes. Each one is bite-sized and interactive, so you make steady progress and pick up exactly where you left off across the web and the app.

Can I write and run code in this Edge Computing with Cloudflare Workers & Deno lesson?

Yes. Every Edge Computing with Cloudflare Workers & Deno lesson includes a built-in code editor, so you write and run real code right in your browser and get instant AI feedback — no local setup required.

All lessons in this course

Deno on Cloudflare Workers
Worker-Deno Project Setup
Shared Logic & Utilities
Deploying & Debugging the Integrated Stack

← Back to Edge Computing with Cloudflare Workers & Deno