0Pricing
Electron Desktop App Development · Aula

Processos em Segundo Plano e Trabalhadores

Use processos em segundo plano e trabalhadores web para transferir cálculos pesados, mantendo a interface principal responsiva e com bom desempenho.

Processos em Segundo Plano e Trabalhadores é uma aula grátis de Electron Desktop App Development no CoddyKit. Esta é a aula 2 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 Electron Desktop App Development, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Electron Desktop App Development inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

Keep Your App Responsive

Imagine your desktop app freezing when you click a button or perform an action. Frustrating, right?

A responsive UI (User Interface) means your application remains smooth and interactive, even when doing heavy work in the background.

This lesson explores how to offload tasks to keep your Electron app feeling snappy and fast for your users.

The Single-Threaded UI

In web browsers and Electron's renderer processes, JavaScript typically runs on a single thread. This is often called the main thread.

This thread handles everything: rendering the UI, responding to user input, and running your JavaScript code.

If a long-running computation happens on the main thread, it "blocks" it, making your app unresponsive and causing the UI to freeze.

Meet Web Workers

To avoid freezing the UI, we can use Web Workers. They allow you to run scripts in the background, separate from the main thread.

Think of a Web Worker as a separate JavaScript execution environment that doesn't interfere with your UI.

They are perfect for CPU-intensive tasks that don't need direct access to the webpage's DOM (Document Object Model).

Your First Web Worker

Let's see a simple example of offloading a "heavy" calculation to a Web Worker.

First, you'd create a file named worker.js containing the worker's logic:

// worker.js content
onmessage = function(e) {
  let result = 0;
  for (let i = 0; i < e.data; i++) {
    result += i;
  }
  postMessage(result); // Send result back to main thread
};

Now, in your Electron renderer process (e.g., within your index.html's <script> or a linked renderer.js), you'd use this code:

Try running this example:

const myWorker = new Worker('./worker.js'); // Path to your worker.js file

myWorker.onmessage = (event) => {
  console.log('Worker finished calculation. Result:', event.data);
  // In a real app, you'd update an HTML element:
  // document.getElementById('resultDisplay').innerText = `Result: ${event.data}`;
};

myWorker.onerror = (error) => {
  console.error('Worker error:', error.message);
};

const dataToSend = 500000000; // A large number for a noticeable delay
console.log('Sending task to worker with input:', dataToSend);
myWorker.postMessage(dataToSend);

console.log('UI thread is free and responsive!');
// This message will appear immediately, proving the UI thread is not blocked.

Talking to Workers

Web Workers communicate with the main thread using a simple message-passing system:

  • postMessage(): Used by both the main thread and the worker to send data.
  • onmessage event handler: Used by both sides to receive data. The data is available in event.data.

Messages are copied, not shared, meaning complex objects are serialized and deserialized. This ensures data integrity between threads.

What Workers Can't Do

While powerful, Web Workers have some limitations:

  • No DOM Access: Workers cannot directly manipulate the webpage's Document Object Model (HTML elements).
  • Limited APIs: They don't have access to some browser APIs like window, document, or parent.
  • Local File Access: Direct access to local files (e.g., using Node.js fs module) is not available in a standard Web Worker.

For tasks requiring these, you might need a different approach or to pass data back to the main thread.

Node.js Worker Threads

Electron's main process, and renderer processes with Node.js integration, can use Node.js Worker Threads.

These are different from Web Workers:

  • They have full Node.js API access (e.g., fs, http).
  • They can be used in the main process to prevent blocking the *entire* Electron app.
  • They are ideal for CPU-bound Node.js tasks.

Worker Threads are crucial when your background tasks need Node.js capabilities.

Node.js Worker in Action

Here's how you might use a Node.js Worker Thread to perform a heavy computation that also uses a Node.js feature (like reading a file, though we'll simplify for the example).

First, create worker_node.js:

// worker_node.js content
const { parentPort } = require('worker_threads');

parentPort.on('message', (data) => {
  let result = 0;
  for (let i = 0; i < data; i++) {
    result += i;
  }
  parentPort.postMessage(result);
});

Then, in your main process or a renderer with Node.js integration:

Try running this example:

const { Worker } = require('worker_threads');
const path = require('path');

// Path to your Node.js worker script (assuming it's in the same directory)
const workerPath = path.join(__dirname, 'worker_node.js');

// Create a new Node.js Worker Thread
const worker = new Worker(workerPath);

// Listen for messages from the worker
worker.on('message', (result) => {
  console.log('Node.js Worker finished. Result:', result);
  worker.terminate(); // Terminate the worker when done
});

// Listen for errors
worker.on('error', (err) => {
  console.error('Node.js Worker error:', err);
});

// Listen for worker exit
worker.on('exit', (code) => {
  if (code !== 0) {
    console.error(`Node.js Worker stopped with exit code ${code}`);
  }
});

// Send data to the worker to start computation
const dataForWorker = 500000000;
console.log('Sending task to Node.js Worker with input:', dataForWorker);
worker.postMessage(dataForWorker);

console.log('Main/Renderer thread is free!');

Web Worker vs. Node.js Worker

How do you decide which type of worker to use?

  • Web Workers:
    • Best for CPU-bound tasks in the renderer process.
    • Cannot access DOM or Node.js APIs.
    • Good for calculations, data processing that doesn't need system access.
  • Node.js Worker Threads:
    • Best for CPU-bound tasks in the main process or renderer process with Node.js integration.
    • Can access all Node.js APIs (e.g., file system, network).
    • Good for heavy Node.js operations without blocking the UI or main app logic.

Worker Knowledge Check

You've learned about different ways to offload tasks in Electron. Let's test your understanding!

Recap: Keeping Electron Responsive

Great job! You've learned how to keep your Electron applications responsive:

  • The main thread handles UI and can be blocked by heavy tasks.
  • Web Workers run JavaScript in the background, separate from the UI, for CPU-bound tasks without DOM access.
  • Node.js Worker Threads also run in the background but provide full Node.js API access, suitable for main process or Node.js-integrated renderer tasks.

By effectively using these tools, you can build Electron apps that feel fast and smooth!

Perguntas Frequentes

A aula “Processos em Segundo Plano e Trabalhadores” é grátis?

Sim — o texto completo de “Processos em Segundo Plano e Trabalhadores” é 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 Electron Desktop App Development, atualize para CoddyKit PRO. O curso de Electron Desktop App Development inclui 4 aulas no total.

O que vou aprender em “Processos em Segundo Plano e Trabalhadores”?

Use processos em segundo plano e trabalhadores web para transferir cálculos pesados, mantendo a interface principal responsiva e com bom desempenho. Você pratica Electron Desktop App Development 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 Electron Desktop App Development?

Nenhuma experiência prévia é necessária. Electron Desktop App Development 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 2 de 4.

Quanto tempo leva a aula “Processos em Segundo Plano e Trabalhadores”?

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 Electron Desktop App Development?

Sim. Cada aula de Electron Desktop App Development 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. Arquiteturas com Várias Janelas
  2. Processos em Segundo Plano e Trabalhadores
  3. Integração com Serviços de Nuvem
  4. Atualizando Automaticamente seu Aplicativo Electron
← Voltar para Electron Desktop App Development