Edge Computing with Cloudflare Workers & Deno · Lección

Lógica y utilidades compartidas

Implemente funciones de utilidad y lógica de negocio compartidas que puedan reutilizarse en entornos de Deno y Workers.

Lógica y utilidades compartidas es una lección gratuita de Edge Computing with Cloudflare Workers & Deno en CoddyKit. Esta es la lección 3 de 4. Puedes leer la lección completa abajo gratuitamente — luego la practicas en el navegador con un editor de código integrado y un tutor de IA 24/7. Forma parte de la ruta de aprendizaje de Edge Computing with Cloudflare Workers & Deno, y tu progreso se sincroniza en la web y la app de CoddyKit. El curso de Edge Computing with Cloudflare Workers & Deno incluye 4 lecciones en total.

Partes de esta lección aún no han sido traducidas y se muestran en inglés.

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!

Preguntas frecuentes

¿La lección «Lógica y utilidades compartidas» es gratis?

Sí — el texto completo de «Lógica y utilidades compartidas» es gratis para leer aquí en la web. Para practicarla de forma interactiva (editor de código integrado y tutor de IA 24/7) y desbloquear el resto del curso de Edge Computing with Cloudflare Workers & Deno, actualiza a CoddyKit PRO. El curso de Edge Computing with Cloudflare Workers & Deno incluye 4 lecciones en total.

¿Qué aprenderé en «Lógica y utilidades compartidas»?

Implemente funciones de utilidad y lógica de negocio compartidas que puedan reutilizarse en entornos de Deno y Workers. Practicas Edge Computing with Cloudflare Workers & Deno con código real que ejecutas directamente en el navegador, y un tutor de IA 24/7 responde tus preguntas mientras trabajas en la lección.

¿Necesito experiencia previa para empezar Edge Computing with Cloudflare Workers & Deno?

No se requiere experiencia previa. Edge Computing with Cloudflare Workers & Deno en CoddyKit está estructurado para principiantes hasta estudiantes avanzados, así que puedes empezar aquí o desde el inicio y avanzar a tu ritmo. Esta es la lección 3 de 4.

¿Cuánto tiempo toma la lección «Lógica y utilidades compartidas»?

La mayoría de las lecciones de CoddyKit toman alrededor de 5–10 minutos. Cada una es compacta e interactiva, así que avanzas constantemente y retomas exactamente por donde dejaste en la web y la app.

¿Puedo escribir y ejecutar código en esta lección de Edge Computing with Cloudflare Workers & Deno?

Sí. Cada lección de Edge Computing with Cloudflare Workers & Deno incluye un editor de código integrado, así que escribes y ejecutas código real directamente en tu navegador y obtienes retroalimentación instantánea de IA — sin configuración local necesaria.

Todas las lecciones de este curso

← Volver a Edge Computing with Cloudflare Workers & Deno