Bypassing Anti-Scraping Protections (CAPTCHA, Rate Limiting)

Industrial anti-scraping protections — DataDome, Cloudflare Bot Management, PerimeterX, Akamai Bot Manager — analyze user behavior across dozens of signals: from WebGL rendering deviations to micro-timings between clicks. Each system uses its own ML models that are updated weekly. Recently, we solved a problem for an e-commerce client: they needed to scrape a competitor's catalog protected by DataDome and reCAPTCHA v3. We applied rotating residential proxies, a modified Playwright with 30+ signature masking, and a custom CAPTCHA solver — stability was 97% at 500,000 pages per day. Such results require deep understanding of the specific protection and combination of several techniques. We implement turnkey bypass: from basic stealth to a full system with monitoring in 12–18 days. Contact us to evaluate your project.

In this article, we'll break down the main types of protections, methods for bypassing rate limiting and CAPTCHA, setting up proxy infrastructure, and ways to maintain stability when algorithms change. Such results require constant monitoring and adaptation — we include this in support.

Classification of Anti-Scraping Protections and How to Tackle Each

Level 1 — Rate limiting. Simple IP-based protection: more than N requests per second → block. Solved by proxy rotation and reducing request frequency.

Level 2 — Browser fingerprinting. Checks navigator.webdriver, canvas fingerprint, WebGL rendering, audio context, plugin list. Detects headless browsers without masking.

Level 3 — Behavioral analysis. ML models on the protection side: mouse movement patterns, timings between actions, event order. Differentiates bots from humans even with correct fingerprint.

Level 4 — CAPTCHA. Visual or behavioral tasks. Google reCAPTCHA v2/v3, hCaptcha, Arkose Labs (FunCaptcha), Cloudflare Turnstile.

We have worked with each of these protections on dozens of projects. Our experience — 5+ years on the market and 30+ successful integrations. We guarantee scraping stability even when protection algorithms are updated. In practice, a combination of several levels is most common, for example, Cloudflare Bot Management + reCAPTCHA v3.

Bypassing Rate Limiting

import asyncio
import random
from aiohttp import ClientSession

async def fetch_with_delay(session, url, semaphore):
    async with semaphore:
        await asyncio.sleep(2 + random.gauss(1, 0.5))  # normal distribution
        async with session.get(url) as resp:
            return await resp.text()

semaphore = asyncio.Semaphore(3)  # max 3 concurrent requests

Random delays with a normal distribution are significantly more effective than fixed ones: the pattern is closer to human behavior.

Stealth Playwright

const { chromium } = require('playwright');
const { stealth } = require('playwright-stealth');

const browser = await chromium.launch({
  args: [
    '--disable-blink-features=AutomationControlled',
    '--no-sandbox',
  ]
});
const context = await browser.newContext({
  userAgent: getRandomUserAgent(),
  locale: 'ru-RU',
  timezoneId: 'Europe/Moscow',
  geolocation: { longitude: 37.6173, latitude: 55.7558 },
  permissions: ['geolocation'],
});
await stealth(context);

playwright-stealth patches over 30 detectable fields: navigator.webdriver, window.chrome, navigator.languages, canvas noise, and more. Using stealth mode is mandatory for sites with behavioral analysis.

Why Proxy Quality Is Critical for Scraping

Protections analyze IP cleanliness and behavior. Residential proxies (Bright Data, Oxylabs) — real IPs from home users — are rarely blocked. Mobile proxies (4G/5G) have a high trust score. Datacenter IPs (AWS, DigitalOcean) are often blacklisted and unsuitable for complex protections. For large projects, residential IPs are worth the investment — the cost of a block is high.

class ProxyRotator:
    def __init__(self, proxies: list):
        self.proxies = proxies
        self.stats = {p: {'success': 0, 'fail': 0} for p in proxies}

    def get_best_proxy(self):
        # select proxy with highest success rate
        return max(
            self.proxies,
            key=lambda p: self.stats[p]['success'] /
                          max(self.stats[p]['success'] + self.stats[p]['fail'], 1)
        )

    def report_success(self, proxy):
        self.stats[proxy]['success'] += 1

    def report_fail(self, proxy):
        self.stats[proxy]['fail'] += 1

How to Bypass CAPTCHA Without Risk of Blocking

Automatic solving via services: 2captcha, Anti-Captcha, CapSolver, NopeCHA. For CAPTCHA v2/v3, tokens from services are used. For reCAPTCHA v3, a high score is needed, achieved through a quality browser profile. (Google reCAPTCHA documentation)

from twocaptcha import TwoCaptcha

solver = TwoCaptcha(API_KEY)

# reCAPTCHA v2
result = solver.recaptcha(
    sitekey='6LfXXXXXXXXXXXXXXXXXXXXX',
    url='https://example.com/page'
)
token = result['code']  # insert into form

Working with Cookies and Sessions

Session cookies are an important signal for protections. A bot that doesn't accumulate cookies over multiple pages looks suspicious.

# Save and restore Playwright context
await context.storage_state(path='session.json')

# In next run
context = await browser.new_context(storage_state='session.json')

For complex sites: first "warm up" the session — visit the homepage, a couple of random pages, simulate scrolling — then proceed to target URLs.

Detecting Protection Algorithm Changes

Protections update algorithms. Monitoring is needed:

• Track HTTP statuses: growth of 403/429/503 → trigger check
• Compare fingerprint requests (JavaScript loaded by DataDome)
• Alerts when successful parse rate drops below threshold

What Our Work Includes

• Analysis of the target site and identification of protection type
• Development and configuration of bypass (stealth, proxies, CAPTCHA)
• Integration with your parser (API, SDK)
• Stability monitoring and automatic adaptation
• Documentation and training for your team

Timelines

Basic bypass rate limiting + stealth: 3–5 days. Full system with CAPTCHA solver, proxy rotator, and monitoring: 12–18 days.

Contact us for a consultation — we'll evaluate your project and offer the optimal solution.

Backend Development Services: Laravel, Node.js, Go, Django, PostgreSQL

On a production server at 3:14 AM, the Laravel Jobs queue stopped processing. 40,000 unprocessed jobs in Redis. Cause: worker crashed due to a memory leak in one of the Jobs (leak via a static variable in an Eloquent observer), supervisor didn't restart it because of misconfigured stopwaitsecs. This is not a hypothetical scenario — it's Tuesday. We analyzed such an incident on a project with 500 RPS load: diagnosis took 4 hours, fix — 20 minutes. So you don't lose money on downtime, we offer backend development services with a focus on production-grade reliability. We'll assess your project in 2 days.

Backend is what works when no one is watching. Or doesn't work. We guarantee you'll have the first option.

How do we ensure production-grade reliability from day one?

What we do correctly from day one

Service Layer over Fat Controllers. Controller receives HTTP request, validates it via Form Request, passes data to Service, returns response. Business logic in Service, not Controller. This sounds trivial, but most legacy projects have controllers with 500 lines and SQL queries inside.

Repository Pattern we use cautiously. If you just wrap Model::where(...) in a repository method — that's boilerplate without benefit. Repository is justified when: you need to abstract from the data source (DB + cache + external API) or when query logic is complex enough to isolate.

Jobs, Events, Listeners. Everything that can be async — make async. Sending email, PDF generation, external API sync, aggregate recalculation — into Queue. Laravel Horizon for queue monitoring in Redis: see throughput, failed jobs, processing time per queue.

How Octane handles high load

Laravel Octane with RoadRunner or Swoole keeps the app in memory between requests — removes bootstrap overhead (config loading, class autoloading) on each HTTP request. Gain: 3–8x on synthetic benchmarks, 2–4x on real applications. Important: no state between requests in static variables — that leads to exactly the incidents from the beginning. We use this in projects with >1000 RPS.

What to do about N+1 queries

N+1 is the most common cause of slow pages in Laravel apps. Standard story: page worked fine on dev with 10 records, on production with 10,000 — 8-second load.

Laravel Debugbar in dev environment shows the number of queries per page. More than 20 queries per page — signal for audit.

Model::preventLazyLoading(! app()->isProduction());

Telescope for profiling in staging: logs all queries, jobs, mail, notifications with time detail. Numbers: after implementing eager loading, page load time drops from 8s to 0.3s — 27 times faster.

PostgreSQL: indexes that are actually needed

PostgreSQL 14+ is the primary DB on all projects. We use PgBouncer + PostgreSQL combination. 10+ years experience, more than 50 backend projects, 5 years on the market.

How PostgreSQL helps avoid slow queries

Composite indexes for frequent WHERE + ORDER BY. If you have WHERE user_id = ? AND status = ? ORDER BY created_at DESC — you need (user_id, status, created_at DESC). A separate index on (user_id) doesn't help much with sorting.

Partial indexes. If 95% of queries go with WHERE status = 'active':

CREATE INDEX idx_orders_active ON orders (created_at DESC)
WHERE status = 'active';

The index is small, fast, covers the main load.

GIN indexes for JSONB and arrays. @> operator without GIN index — seq scan. With index — fast even on millions of rows.

GIN for full-text search. to_tsvector + GIN instead of LIKE '%query%'. LIKE without index is always seq scan. With pg_trgm extension and gin_trgm_ops — supports LIKE with index, useful for CRM search by partial match.

Connection pooling: why it's more important than it seems

Rails, Laravel, Django open a new connection to PostgreSQL for each PHP/Python process. With 100 workers — 100 connections. PostgreSQL starts degrading from 200–300 active connections — overhead on connection management becomes significant.

PgBouncer — connection pooler in front of PostgreSQL. Transaction pooling mode: connection to PostgreSQL is occupied only during a transaction, returned to pool between requests. 1000 application workers → 20–50 actual connections to PostgreSQL. This reduces latency by 40% and hosting costs by 30%.

Node.js with Fastify: when it's better than Laravel

Node.js is justified for:

• Realtime: WebSocket servers, Server-Sent Events, chat, live updates
• Streaming: large files, video, streaming data
• High I/O concurrency: many parallel requests to external APIs without heavy business logic
• Serverless: Lambda/Cloud Functions — Node.js starts faster than PHP

Fastify over Express: 2–3 times faster on benchmarks, built-in JSON Schema validation, better TypeScript support, plugin architecture.

Typical realtime architecture: Laravel — core business logic and REST API. Node.js + Socket.io or ws — WebSocket server. Laravel publishes events to Redis Pub/Sub, Node.js subscribes and broadcasts to clients. This separation allows scaling the WebSocket server independently of the main app.

Go: microservices and high load

Go we use for:

• High-load microservices (>10,000 RPS)
• Background workers with strict latency requirements
• DevOps tools and CLI
• gRPC services in microservice architecture

Goroutines — thousands of times cheaper than OS threads. 10,000 concurrent connections on Go is normal on one server.

But Go is not a silver bullet. Development is slower than Laravel: more boilerplate, no ORM at Eloquent level, error handling with if err != nil everywhere. Justified only when performance is a real requirement, not an assumption.

Django and Python backend

Django with DRF (Django REST Framework) — for tasks where Python is needed: ML pipelines, data processing, integrations with AI tools.

Celery for background tasks — similar to Laravel Queue but more complex to configure. Celery Beat for cron tasks.

Django ORM vs raw SQL: ORM is convenient for CRUD. For analytical queries with multiple JOINs, window functions, and CTEs — connection.execute() with raw SQL is more readable and predictable.

Redis: not just cache

Redis in our projects plays multiple roles:

Redis Cluster for horizontal scaling. Sentinel for automatic failover on standalone setups.

Deployment and infrastructure

Docker + docker-compose — standard for local development and production. Each service in a container: PHP-FPM/Octane, Nginx, PostgreSQL, Redis, Queue Worker, Scheduler.

CI/CD via GitHub Actions:

1. Run tests (PHPUnit / Pest, Vitest, Playwright)
2. Build Docker image
3. Push to Container Registry
4. Deploy: docker pull → docker-compose up -d on server, or Kubernetes rolling update

Zero-downtime deploy for Laravel: php artisan down --secret=TOKEN is not needed with proper configuration. Strategy: new container starts next to the old one, Nginx switches traffic after health check, old container stops.

Monitoring: Sentry for exception tracking with alerting in Slack/Telegram. Grafana + Prometheus (or Grafana Cloud) for metrics: CPU, memory, request rate, queue depth, database connection count. Alerts on: error rate > 1%, p99 latency > 2s, queue depth > 1000 jobs.

What's included in turnkey work

• Architecture design (API documentation, DB schema, service diagram)
• Implementation according to agreed specification with code review
• CI/CD, monitoring, alerting setup
• Load testing (k6, wrk) with report
• Handover of source code, access, deployment instructions
• Training of customer's team (2-3 sessions)
• Warranty support for 1 month after delivery

Timeline benchmarks

Pricing is calculated individually after analyzing load, integrations, and business logic. Contact us for a free audit of your current backend — get an optimization plan in 2 days. Request a consultation.