Micro Frontends Architecture with Module Federation · درس

حلول التواصل المخصّصة

صمّم ونفّذ آليات تواصل مخصّصة ومهيأة لتلبية احتياجات Micro Frontend المحددة

حلول التواصل المخصّصة درس مجاني في Micro Frontends Architecture with Module Federation على CoddyKit. هذا هو الدرس 3 من أصل 4. يمكنك قراءة الدرس كاملاً أدناه مجاناً — ثم تمرن عليه مباشرة في المتصفح باستخدام محرر أكواد مدمج ومدرس ذكاء اصطناعي متاح 24/7. هذا الدرس جزء من مسار التعلم في Micro Frontends Architecture with Module Federation، وتقدمك يتزامن عبر الويب وتطبيق CoddyKit. تتضمن دورة Micro Frontends Architecture with Module Federation 4 دروس في المجموع.

بعض أجزاء هذا الدرس لم تُترجم بعد وتظهر باللغة الإنجليزية.

Beyond Standard Communication

In Micro Frontend architectures, communication between different parts is crucial. We've explored event buses and shared state management.

However, sometimes your specific needs might call for more tailored approaches. This lesson dives into designing and implementing custom communication solutions.

Why Custom Solutions?

Why would you choose a custom solution over an established pattern?

Specific Interaction: When a very particular, direct interaction is needed.
Performance: To optimize for very high-frequency or low-latency communication.
Minimal Overhead: For simple, ad-hoc needs without bringing in heavy libraries.
Tight Coupling (Rare): In scenarios where two MFEs are intentionally very close and share a parent context.

Direct Callback Passing

One custom approach involves passing functions (callbacks) directly from a host application to a remote application as props or arguments. This is suitable when a host component directly renders a remote component and needs to react to its actions.

Module Federation allows you to share functions just like components or data.

Example: Passing a Callback

Imagine a host passing a 'notify' function to a remote, which then calls it. This is a simplified JavaScript representation:

function hostApp() {
  function handleNotification(message) {
    console.log(`Host received: ${message}`);
  }

  // In a real MFE, remote would be loaded
  // and `onNotify` passed as a prop.
  // For demo, we'll simulate the call.
  console.log("Host ready to receive.");
  remoteApp(handleNotification);
}

function remoteApp(onNotify) {
  console.log("Remote app started.");
  setTimeout(() => {
    onNotify("Data processed successfully!");
  }, 1000);
}

hostApp();

Browser's postMessage API

The postMessage API is a powerful browser feature for secure cross-origin communication between windows, iframes, and Web Workers.

It's ideal for sending messages between a host and an embedded MFE (e.g., in an iframe) where direct JavaScript access is restricted due to security policies.

Example: postMessage (Conceptual)

This is how a host and remote (e.g., in an iframe) would conceptually use postMessage to communicate. Note: This requires a browser environment to run fully.

// Host (parent window):
// const iframe = document.getElementById('remote-mfe');
// iframe.contentWindow.postMessage('Hello from Host!', 'http://remote.com');
// window.addEventListener('message', (event) => {
//   if (event.origin === 'http://remote.com') {
//     console.log('Host received:', event.data);
//   }
// });

// Remote (inside iframe):
// window.addEventListener('message', (event) => {
//   if (event.origin === 'http://host.com') {
//     console.log('Remote received:', event.data);
//     event.source.postMessage('Hello from Remote!', event.origin);
//   }
// });

// This snippet simulates the message flow:
function simulatePostMessage() {
  console.log("Simulating postMessage...");
  const hostMessage = "Hello from Host!";
  const remoteMessage = "Hello from Remote!";

  // Host sends to Remote
  console.log(`Host sends: "${hostMessage}"`);

  // Remote receives and replies
  console.log(`Remote receives: "${hostMessage}"`);
  console.log(`Remote sends: "${remoteMessage}"`);

  // Host receives reply
  console.log(`Host receives: "${remoteMessage}"`);
}

simulatePostMessage();

Shared Global Registry/Service

For specific, limited global data or services, you can create a custom JavaScript object or class and expose it via Module Federation's shared scope.

This acts like a lightweight, custom singleton that all federated applications can access and interact with, without full state management.

Example: Custom Shared Registry

Here's a simple custom registry object that could be shared. Each MFE could import and use mySharedRegistry.

// mySharedRegistry.js (exposed via Module Federation)
const mySharedRegistry = {
  _data: {},
  set: function(key, value) {
    this._data[key] = value;
    console.log(`Registry updated: ${key} = ${value}`);
  },
  get: function(key) {
    return this._data[key];
  },
  getAll: function() {
    return { ...this._data };
  }
};

// Simulate usage in different MFEs
console.log("--- MFE A ---");
mySharedRegistry.set("userTheme", "dark");

console.log("--- MFE B ---");
console.log(`Current user theme: ${mySharedRegistry.get("userTheme")}`);
mySharedRegistry.set("appVersion", "1.0.1");

console.log("--- MFE A (again) ---");
console.log(`Current app version: ${mySharedRegistry.get("appVersion")}`);

Considerations & Trade-offs

While custom solutions offer flexibility, they come with trade-offs:

Increased Coupling: Can make MFEs less independent.
Complexity: Harder to maintain and debug compared to standard patterns.
Scalability: May not scale well if communication needs grow.
Security: `postMessage` needs careful origin validation.

Always weigh the benefits against these potential drawbacks.

Custom Communication Check

You're implementing a Micro Frontend architecture. One MFE is embedded in an iframe on a different domain. You need to send simple messages between the host and the iframe securely.

Recap: Custom Solutions

We explored custom communication solutions for Micro Frontends, going beyond event buses and shared state.

Direct Callbacks: For tightly coupled components.
postMessage API: For secure cross-origin communication, especially with iframes.
Shared Registries: For lightweight, custom global data/services.

Remember to carefully consider the trade-offs of increased coupling and complexity before opting for a custom approach.

الأسئلة الشائعة

هل درس «حلول التواصل المخصّصة» مجاني؟

نعم — نص درس «حلول التواصل المخصّصة» كامل متاح مجاناً هنا على الويب. لتمرينه بشكل تفاعلي (محرر أكواد مدمج ومدرس ذكاء اصطناعي متاح 24/7) وفتح باقي دورة Micro Frontends Architecture with Module Federation، انتقل إلى CoddyKit PRO. تتضمن دورة Micro Frontends Architecture with Module Federation 4 دروس في المجموع.

ماذا ستتعلم في «حلول التواصل المخصّصة»؟

صمّم ونفّذ آليات تواصل مخصّصة ومهيأة لتلبية احتياجات Micro Frontend المحددة تتمرن على Micro Frontends Architecture with Module Federation مع أكواد عملية تشغلها مباشرة في المتصفح، ومدرس ذكاء اصطناعي متاح 24/7 يجيب على أسئلتك أثناء عملك.

هل أحتاج إلى خبرة سابقة لأبدأ Micro Frontends Architecture with Module Federation؟

لا تُشترط خبرة سابقة. Micro Frontends Architecture with Module Federation على CoddyKit منظم للمبتدئين حتى المتقدمين، لذا يمكنك البدء من هنا أو من البداية والتقدم بسرعتك الخاصة. هذا هو الدرس 3 من أصل 4.

كم من الوقت يستغرق درس «حلول التواصل المخصّصة»؟

معظم دروس CoddyKit تستغرق حوالي 5–10 دقائق. كل منها موجز وتفاعلي، لذا تحرز تقدماً مستمراً وتستأنف من حيث توقفت عبر الويب والتطبيق.

هل يمكنني كتابة وتشغيل أكواد في درس Micro Frontends Architecture with Module Federation هذا؟

نعم. كل درس في Micro Frontends Architecture with Module Federation يتضمن محرر أكواد مدمج، لذا تكتب وتشغل أكواداً حقيقية مباشرة في متصفحك وتحصل على تعليقات فورية من الذكاء الاصطناعي — بدون إعداد محلي.

جميع الدروس في هذه الدورة

← العودة إلى Micro Frontends Architecture with Module Federation