Logika & Utilitas Bersama
Implementasikan fungsi utilitas dan logika bisnis bersama yang dapat digunakan kembali di lingkungan Deno dan Worker.
Logika & Utilitas Bersama adalah pelajaran Edge Computing with Cloudflare Workers & Deno gratis di CoddyKit. Ini adalah pelajaran 3 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Edge Computing with Cloudflare Workers & Deno, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Edge Computing with Cloudflare Workers & Deno mencakup 4 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
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 theenvobject passed tofetch. - File System Access: Available in Deno, not directly in Workers.
- Global Objects: Be mindful of differences in global APIs (though
fetchis 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!
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Logika & Utilitas Bersama” gratis?
Ya — teks lengkap “Logika & Utilitas Bersama” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Edge Computing with Cloudflare Workers & Deno, upgrade ke CoddyKit PRO. Kursus Edge Computing with Cloudflare Workers & Deno mencakup 4 pelajaran total.
Apa yang akan aku pelajari di “Logika & Utilitas Bersama”?
Implementasikan fungsi utilitas dan logika bisnis bersama yang dapat digunakan kembali di lingkungan Deno dan Worker. Kamu berlatih Edge Computing with Cloudflare Workers & Deno dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai Edge Computing with Cloudflare Workers & Deno?
Tidak diperlukan pengalaman sebelumnya. Edge Computing with Cloudflare Workers & Deno di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 3 dari 4.
Berapa lama pelajaran “Logika & Utilitas Bersama” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran Edge Computing with Cloudflare Workers & Deno ini?
Ya. Setiap pelajaran Edge Computing with Cloudflare Workers & Deno menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Deno di Cloudflare Workers
- Penyiapan Proyek Worker-Deno
- Logika & Utilitas Bersama
- Menerapkan dan Men-debug Tumpukan Terintegrasi