Scaling for Production
Last updated
Last updated
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.
Option 1: Manage scaling yourself: Leverage Reacher's statelessness and decide yourself how to deploy Reacher.
Option 2: RabbitMQ-based Queue Architecture: Reacher includes a pre-integrated queue system based on RabbitMQ, enabling efficient task management and scaling.
Alternative scaling solutions were also explored, chat with if you want to discuss more.
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:
Purchase a Commercial License. This will grant you access to an unrestricted Dockerfile.
Purchase 3rd-party proxy IPs. You will receive configuration details for the proxy to be passed into the unrestricted Dockerfile.
Get in touch with when you're there.