Scaling for Production

Reacher's stateless architecture enables efficient horizontal scaling, allowing companies to tailor deployments to their specific needs. Below are the scaling options and pathways for a production setup.

  1. Manage scaling yourself: Leverage Reacher's statelessness and decide yourself how to deploy Reacher.

  2. Option 1: RabbitMQ-based Queue Architecture: Reacher includes a pre-integrated queue system based on RabbitMQ, enabling efficient task management and scaling.

  3. Option 2: AWS SQS + Lambda (coming soon... or ask [email protected])

Alternative scaling solutions were also explored, chat with [email protected] if you want to discuss more.

Scaling beyond the Commercial License Trial

The documentation in this section mentions the Dockerfile provided as part of the Commercial License Trial, which:

  • has a built-in proxy,

  • limits the number of daily verifications to 10000.

The strategies documented in this section apply both to the Commercial License Trial as well as a high-volume setup beyond this limit. Once you're ready to transition from the former to the latter, you must:

  1. Purchase a Commercial License. This will grant you access to an unrestricted Dockerfile.

  2. Purchase 3rd-party proxy IPs. You will receive configuration details for the proxy to be passed into the unrestricted Dockerfile.

Get in touch with [email protected] when you're there.

Last updated