API Throttling Implementation for Web Applications

Picture this: your backend handles 1000 requests per second, but suddenly a partner service starts sending 10,000 webhooks per minute. Without throttling, the server goes down, 500 errors flood in, and users leave. In one e-commerce project, implementing throttling delivered significant savings by reducing load and eliminating the need for extra instances. Throttling is the only way to maintain control: it doesn't reject requests but slows them down or queues them, giving the backend time to breathe.

Throttling manages the rate of request processing at the server level, as opposed to rate limiting, which restricts the client. The difference is fundamental: rate limiting says "you made too many requests," while throttling says "we process as many as we can." Both approaches work together — that's how we protect both clients and infrastructure. Protecting APIs from overload is the primary goal of throttling. In one project, implementing throttling reduced 500 errors from 15% to 0.5% and cut p95 latency from 1200 ms to 200 ms.

Why Throttling Is Essential for High-Load APIs

Without throttling, peak loads cause cascading failures: overloaded backend stops responding, nginx times out, clients retry — and the load increases. Throttling smooths out spikes, allowing the server to run stably. In our projects, implementing throttling reduced the number of 500 errors by 90% and decreased p95 latency by 40%.

Throttling vs Rate Limiting

In practice, both mechanisms are used together. For example, during a flash sale at a retailer, rate limiting blocks clients exceeding their limit, while throttling queues valid requests to prevent the backend from crashing.

Comparison of Adaptive Throttling Methods

Throttling Heavy Operations

Some operations — exporting reports, processing files, sending email campaigns — should not run in parallel without limits. BullMQ with a rate limiter is 10 times more efficient than a manual queue with setTimeout — we verified this in load tests.

// BullMQ — throttle via concurrency + rateLimit
const queue = new Queue('reports', { connection: redis });

const worker = new Worker('reports', processReport, {
  connection: redis,
  concurrency: 5,            // max 5 parallel tasks
  limiter: {
    max: 10,                 // 10 tasks
    duration: 60_000,        // per 60 seconds
  },
});

// Adding a task with priority
await queue.add('generate-csv', { userId, filters }, {
  priority: user.plan === 'enterprise' ? 1 : 10,
  attempts: 3,
  backoff: { type: 'exponential', delay: 2000 },
});

How Adaptive Throttling Prevents Failures

Adaptive throttling dynamically adjusts limits in response to server metrics. When p95 latency exceeds 500 ms or error rate rises, the limit decreases; when normalizing, it increases:

class AdaptiveThrottler {
  private limit = 100;
  private readonly minLimit = 10;
  private readonly maxLimit = 100;

  async check(): Promise<boolean> {
    const metrics = await this.getMetrics();

    // Reduce limit when p95 latency is high
    if (metrics.p95Latency > 500) {
      this.limit = Math.max(this.minLimit, this.limit * 0.8);
    } else if (metrics.p95Latency < 200 && metrics.errorRate < 0.01) {
      this.limit = Math.min(this.maxLimit, this.limit * 1.1);
    }

    return this.counter.increment() <= this.limit;
  }
}

Google uses a similar mechanism in its services (Client-Side Throttling from SRE book).

Circuit Breaker for External APIs

Throttling for outgoing requests uses the Circuit Breaker pattern. It prevents cascading failures if an external service is unavailable. The Opossum library implements this pattern in Node.js:

import CircuitBreaker from 'opossum';

const options = {
  timeout: 3000,          // request > 3 seconds = fail
  errorThresholdPercentage: 50, // 50% errors → open
  resetTimeout: 30000,    // try again after 30 sec (half-open)
  volumeThreshold: 10,    // at least 10 requests for calculation
};

const breaker = new CircuitBreaker(callExternalAPI, options);

breaker.on('open', () => logger.warn('Circuit breaker OPEN — external API unavailable'));
breaker.on('halfOpen', () => logger.info('Circuit breaker HALF-OPEN — testing'));
breaker.on('close', () => logger.info('Circuit breaker CLOSE — external API recovered'));

// Fallback when circuit is open
breaker.fallback(() => ({ status: 'cached', data: getCachedData() }));

States: Closed (normal) → Open (too many errors, requests blocked) → Half-Open (test request) → Closed (if successful).

Throttling Incoming Webhooks

Partners can send thousands of webhooks simultaneously (e.g., during bulk order status updates). The correct pattern is to accept quickly (202), then queue. Below is an example in Laravel using Horizon:

// WebhookController.php — immediate response
public function handle(Request $request)
{
    $payload = $request->all();
    $signature = $request->header('X-Signature');

    if (!$this->verifySignature($payload, $signature)) {
        return response()->json(['error' => 'Invalid signature'], 401);
    }

    // Put on a throttled queue
    ProcessWebhook::dispatch($payload)
        ->onQueue('webhooks')
        ->delay(now()); // immediate, but through queue

    return response()->json(['accepted' => true], 202);
}

// config/queue.php — worker limit for webhooks queue
// Horizon:
'webhooks' => [
    'connection' => 'redis',
    'queue' => ['webhooks'],
    'balance' => 'auto',
    'maxProcesses' => 10, // no more than 10 parallel
],

limit_req_zone $binary_remote_addr zone=api:10m rate=10r/s;

server {
    location /api/ {
        limit_req zone=api burst=20 nodelay;
    }
}

Monitoring Throttling

Metrics for the dashboard: queue depth, p95 latency, number of rejected/delayed requests, error rate. We use Prometheus for collection and Grafana for visualization. Alert: queue depth > 1000 for 5 minutes → Scale up workers or notify the on-call engineer.

What's Included in Throttling Implementation

1. Audit current bottlenecks (collect metrics, profiling)
2. Design throttling scheme (queues, circuit breaker, adaptive logic)
3. Develop and integrate code (BullMQ, Opossum, custom utilities)
4. Configure monitoring and alerts (Prometheus + Grafana)
5. Operational documentation and load testing
6. Guarantee stable operation under load, 10+ years of experience

Timelines

Basic implementation (queue + circuit breaker) — 3–5 days. With adaptive throttling, metrics, and dashboard — 1–2 weeks. The cost is calculated individually — contact us and we'll evaluate your project.

Get a consultation from an engineer — we'll analyze your architecture and choose the optimal solution. Order throttling implementation with a guaranteed result.

Web Application Security: HTTPS, CSP, XSS, CSRF, WAF, DDoS Protection

A website breach rarely looks like in movies. More often it's: a bot finds an unprotected /admin/export endpoint, downloads the customer database, and closes the connection. Or: through an outdated WordPress plugin, a web shell is uploaded, and the server starts sending spam. Or quieter: an XSS in a comment field allows stealing admin session cookies, unnoticed for months. We have analyzed dozens of such cases — each vulnerability could have been fixed at the development or audit stage.

Web application security is not a single setting. It's layers of protection, each closing a separate class of attacks. Order an audit — we'll assess the project and deliver a turnkey plan within 2–4 weeks.

How do we ensure comprehensive web application security?

HTTPS and Proper TLS Configuration

HTTPS is the minimum mandatory level. But having an SSL certificate and having a properly configured TLS are different things.

In Nginx/Apache configuration we check:

• Protocols: only TLS 1.2 and TLS 1.3, SSLv3 and TLS 1.0/1.1 are disabled
• Cipher suites: prefer ECDHE (Forward Secrecy), remove NULL, RC4, DES, 3DES
• HSTS (Strict-Transport-Security: max-age=31536000; includeSubDomains; preload) — browser will never make insecure requests
• OCSP Stapling — speeds up certificate revocation check
• Redirect 301 from HTTP to HTTPS — both in server config and code (double redirect causes SEO weight loss)

Check: SSL Labs (ssllabs.com/ssltest) should show A or A+. If B, the configuration is weak.

Let's Encrypt + Certbot for production is standard. Automatic renewal via certbot renew in cron. Wildcard certificates for subdomains via DNS-01 challenge.

Content Security Policy: The Most Powerful and Complex Protection

CSP is an HTTP header that tells the browser which sources are allowed to load resources. A properly configured CSP completely blocks most XSS attacks, even if the vulnerability exists in the code.

The problem: breaking the site with an incorrect CSP is easy. default-src 'none' — and fonts, images, JS stop working. So we start with Content-Security-Policy-Report-Only — CSP logs violations but does not block anything. We monitor reports for 2–4 weeks, refine the policy, then switch to enforcement mode.

Example of a real policy for a site with Google Analytics, Google Fonts, and Stripe:

Content-Security-Policy:
  default-src 'self';
  script-src 'self' https://www.googletagmanager.com https://js.stripe.com 'nonce-{random}';
  style-src 'self' https://fonts.googleapis.com 'unsafe-inline';
  font-src 'self' https://fonts.gstatic.com;
  frame-src https://js.stripe.com;
  img-src 'self' data: https://www.google-analytics.com;
  connect-src 'self' https://api.stripe.com https://www.google-analytics.com;
  report-uri /csp-report;

nonce — a random string generated server-side per request. Inline scripts with the correct nonce are allowed; without nonce, they are blocked. This completely breaks XSS via <script>alert(1)</script>.

'unsafe-inline' in style-src is a compromise for inline styles. It's better to remove it by moving all styles to CSS files, but that requires refactoring.

Why XSS Remains the Most Common Vulnerability?

XSS (Cross-Site Scripting) — injection of JS code through user input. According to OWASP, XSS is in the top 3 web application vulnerabilities. Three types:

Protection: never insert user input into HTML without escaping. In PHP — htmlspecialchars() with ENT_QUOTES. In Laravel Blade templates — {{ $var }} is safe, {!! $var !!} is dangerous. In React — {variable} is safe, dangerouslySetInnerHTML is dangerous. For Rich Text — use htmlpurifier on PHP or DOMPurify in the browser.

CSRF: Protecting Forms and APIs

CSRF (Cross-Site Request Forgery) — an attacker forces the victim's browser to send a request on their behalf. Example: a user is logged into a bank, opens a malicious page, which makes fetch('https://bank.ru/transfer?to=evil&amount=50000') — if the bank is unprotected, money is transferred.

CSRF tokens — standard protection for forms: the server generates a random token, stores it in the session, and inserts it as a hidden field in the form. On POST request, the token is verified. The attacker does not know the token. Laravel does this automatically with @csrf.

SameSite cookies — modern protection: SameSite=Strict or SameSite=Lax prevents the browser from sending cookies in cross-site requests. Works in all modern browsers.

API without sessions (JWT, Bearer tokens) — CSRF is irrelevant if the token is not stored in a cookie (but in the Authorization header or localStorage). However, localStorage is vulnerable to XSS — so for sensitive data, HttpOnly cookies with SameSite are preferable.

WAF and DDoS Protection

WAF (Web Application Firewall) filters HTTP traffic for attacks: SQL injection, XSS, path traversal, known exploit patterns. Options:

• Cloudflare WAF — cloud-based, OWASP Top 10 rules out of the box, custom rules via expressions. Managed Rules automatically block new threats.
• ModSecurity (Nginx/Apache) — self-hosted, OWASP Core Rule Set (CRS). Flexible but requires tuning and monitoring of false positives.
• AWS WAF — for infrastructure on AWS, integrates with CloudFront and ALB.

DDoS protection. Cloudflare at L3/L4/L7 is the de facto standard for most sites. Automatic mitigation of volumetric attacks, Under Attack Mode during active attacks. For critical infrastructure — Cloudflare Magic Transit or specialized solutions (Qrator, StormWall for the Russian market).

Rate Limiting at the application level — an additional layer. Laravel ThrottleRequests middleware: 60 requests per minute per IP for general endpoints, 5 for /login and /password/reset. Redis as a counter store — mandatory for horizontally scalable systems (otherwise limits are not synchronized between servers).

Other Mandatory Measures

Security headers. Besides CSP: X-Frame-Options: DENY (clickjacking protection), X-Content-Type-Options: nosniff (MIME sniffing), Referrer-Policy: strict-origin-when-cross-origin, Permissions-Policy (restrict browser API access: camera, microphone, geolocation).

SQL injection. Prepared statements everywhere. No concatenation of user input into SQL strings. ORM (Eloquent, Doctrine) protects by default. $wpdb->prepare() in WordPress is mandatory.

Dependency updates. composer audit and npm audit in CI/CD pipeline. Dependabot or Renovate for automatic PRs with updates. Critical CVEs — patch within 24 hours.

Secrets and configuration. .env — never in Git. Secrets in production — via CI/CD environment variables (GitHub Secrets, GitLab CI Variables) or HashiCorp Vault. Leak detection: git-secrets, truffleHog in pre-commit hooks.

How We Work

1. Audit — code scanning, configuration review, dependency analysis, manual business logic verification.
2. Planning — vulnerability remediation plan, stack selection (CSP, WAF, rate limiting).
3. Implementation — TLS setup, CSP configuration, headers, Rate Limiting, WAF.
4. Testing — re-penetration test, load testing, false positive check.
5. Deployment and Monitoring — enable production CSP, set up alerts, train the team.

What's Included

• Report with found vulnerabilities and recommendations (PDF + code snippets)
• Ready TLS configuration (Nginx/Apache)
• CSP policy with Report-Only and production versions
• WAF and Rate Limiting setup
• Dependency update plan
• Access to monitoring tools (Sentry, Datadog)
• 30 days of post-audit support (consultations, fixes)

Timeline and Cost

The budget is calculated individually — contact us for a project evaluation.