0Pricing
Edge Computing with Cloudflare Workers & Deno · Aula

Lógica e utilitários compartilhados

Implemente funções utilitárias e lógica de negócio compartilhadas, que possam ser reutilizadas nos ambientes Deno e Worker.

Lógica e utilitários compartilhados é uma aula grátis de Edge Computing with Cloudflare Workers & Deno no CoddyKit. Esta é a aula 3 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Edge Computing with Cloudflare Workers & Deno, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Edge Computing with Cloudflare Workers & Deno inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em 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!

Perguntas Frequentes

A aula “Lógica e utilitários compartilhados” é grátis?

Sim — o texto completo de “Lógica e utilitários compartilhados” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Edge Computing with Cloudflare Workers & Deno, atualize para CoddyKit PRO. O curso de Edge Computing with Cloudflare Workers & Deno inclui 4 aulas no total.

O que vou aprender em “Lógica e utilitários compartilhados”?

Implemente funções utilitárias e lógica de negócio compartilhadas, que possam ser reutilizadas nos ambientes Deno e Worker. Você pratica Edge Computing with Cloudflare Workers & Deno com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar Edge Computing with Cloudflare Workers & Deno?

Nenhuma experiência prévia é necessária. Edge Computing with Cloudflare Workers & Deno no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 3 de 4.

Quanto tempo leva a aula “Lógica e utilitários compartilhados”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de Edge Computing with Cloudflare Workers & Deno?

Sim. Cada aula de Edge Computing with Cloudflare Workers & Deno inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

  1. Deno no Cloudflare Workers
  2. Configuração do projeto Worker-Deno
  3. Lógica e utilitários compartilhados
  4. Implantando e depurando a pilha integrada
← Voltar para Edge Computing with Cloudflare Workers & Deno