Browser-task & Server-task

FilesWorkflow supports two types of tasks: Browser-tasks and Server-tasks.

1. Browser-tasks:

   • Run directly in the user's web browser.

   • Leverage browser-specific features and APIs.

   • Ideal for client-side operations like file transformations.

   • Limited by browser capabilities and security restrictions.

2. Server-tasks:

   • Execute on cloud servers.

   • Utilize Node.js runtime (currently version 20).

   • Suitable for more complex or resource-intensive operations.

   • Can access server-side libraries and perform operations not possible in browsers.

   • Support environment variables for secure handling of sensitive information: • Set up in task configuration. • Injected at runtime. • Accessible within the task code. • Ideal for API keys, credentials, or other sensitive data.

3. Combining Tasks:

   • Workflows can include both browser-tasks and server-tasks.

   • Allows for flexible and powerful processing pipelines.

   • Optimize performance by choosing the appropriate task type for each operation.