Bright Data Worker Deployment

Overview

Deploy collection as bounded workers instead of one privileged process. Separate synchronous proxy or Browser API requests from scraper triggers, snapshot polling, downloads, and destination delivery so each stage has its own authority, queue, resource ceiling, and rollback.

Prerequisites

• An approved workload manifest naming targets, fields, products, and destinations
• Managed secret references and environment-specific Bright Data resources
• Queue, object-storage, quarantine, and observability facilities

Instructions

Step 1: Inventory runtime responsibilities

Read the application and Grep for proxy requests, Browser API sessions, /datasets/v3/trigger, progress checks, snapshot downloads, and delivery calls. Assign each responsibility to the smallest worker role.

Step 2: Define admission and isolation