Pembatasan Laju dan Throttling
Terapkan pembatasan laju dan throttling untuk melindungi API dari penyalahgunaan serta memastikan penggunaan yang adil bagi semua klien.
Pembatasan Laju dan Throttling adalah pelajaran NestJS Enterprise Backend APIs gratis di CoddyKit. Ini adalah pelajaran 1 dari 3. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar NestJS Enterprise Backend APIs, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus NestJS Enterprise Backend APIs mencakup 3 pelajaran total.
Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.
What is Rate Limiting?
Imagine a popular API. Without limits, a single user or malicious bot could flood it with requests, slowing it down for everyone or even crashing it.
Rate limiting is a technique to control the number of requests a client can make to a server within a specific time window. It's like a bouncer at a club, ensuring fair entry for all.
Protecting Your API
Rate limiting is vital for several reasons:
- Prevent Abuse: Stops bots and malicious users from overwhelming your API.
- Ensure Fair Usage: Guarantees that all users get a reasonable share of API resources.
- DDoS Protection: A basic layer of defense against distributed denial-of-service attacks.
- Cost Management: For cloud-based services, too many requests can lead to higher bills.
Rate Limiting in Action
Let's see a simple example of how a rate limiter might work behind the scenes. This script tracks requests from different "IP addresses" and allows only a certain number within a time window.
const requestCounts = new Map<string, { count: number; resetTime: number }>();
const LIMIT = 3; // Max 3 requests
const WINDOW_MS = 5000; // per 5 seconds
function checkRateLimit(ip: string): boolean {
const now = Date.now();
let entry = requestCounts.get(ip);
if (!entry || now > entry.resetTime) {
entry = { count: 1, resetTime: now + WINDOW_MS };
requestCounts.set(ip, entry);
return true; // Request allowed
}
if (entry.count < LIMIT) {
entry.count++;
requestCounts.set(ip, entry);
return true; // Request allowed
}
return false; // Request denied
}
// Simulate requests for IP "192.168.1.1"
console.log("Req 1 (IP A):", checkRateLimit("192.168.1.1"));
console.log("Req 2 (IP A):", checkRateLimit("192.168.1.1"));
console.log("Req 3 (IP A):", checkRateLimit("192.168.1.1"));
console.log("Req 4 (IP A):", checkRateLimit("192.168.1.1")); // Denied
console.log("Req 1 (IP B):", checkRateLimit("192.168.1.2"));What is Throttling?
While often used interchangeably, throttling has a subtle difference. Rate limiting is a hard cap: once you hit the limit, you're blocked.
Throttling, however, aims to smooth out the request rate, often by delaying requests or allowing a slower, sustained rate rather than blocking entirely. It's more about resource management and preventing a system from becoming overloaded.
Introducing NestJS Throttler
NestJS provides a robust solution for both rate limiting and throttling through the @nestjs/throttler package. It's built on top of the express-rate-limit or fastify-rate-limit packages, offering a declarative way to protect your endpoints.
The module uses a guard to intercept requests and apply rules before they reach your controller logic.
Global Throttling Configuration
First, install the package. Then, integrate ThrottlerModule into your root module (AppModule) and apply the ThrottlerGuard globally.
// 1. Install package
// npm install @nestjs/throttler
// 2. src/app.module.ts
import { Module } from '@nestjs/common';
import { ThrottlerModule, ThrottlerGuard } from '@nestjs/throttler';
import { APP_GUARD } from '@nestjs/core'; // For global guard
@Module({
imports: [
ThrottlerModule.forRoot([{
ttl: 60000, // Time to live (1 minute)
limit: 10 // Max 10 requests
}]),
],
providers: [
{
provide: APP_GUARD,
useClass: ThrottlerGuard,
},
],
})
export class AppModule {}Overriding Limits per Route
Sometimes, you need different limits for specific endpoints. For example, a login route might have a stricter limit than a public data endpoint. You can override the global settings using the @Throttle() decorator.
// src/app.controller.ts
import { Controller, Get } from '@nestjs/common';
import { Throttle } from '@nestjs/throttler';
@Controller('posts')
export class PostsController {
@Get()
findAll(): string {
return 'This is a public list of posts.';
}
@Throttle({ default: { limit: 3, ttl: 60000 } }) // 3 req/min
@Get('protected')
findProtected(): string {
return 'This is a protected list of posts.';
}
@Throttle({ default: { limit: 1, ttl: 5000 } }) // 1 req/5s
@Get('critical')
findCritical(): string {
return 'Accessing critical data.';
}
}Skipping Throttling
There might be routes you want to completely exempt from any throttling rules, such as health check endpoints or webhook receivers that expect high traffic. Use the @SkipThrottle() decorator for this.
// src/status.controller.ts
import { Controller, Get } from '@nestjs/common';
import { SkipThrottle } from '@nestjs/throttler';
@Controller('status')
export class StatusController {
@SkipThrottle() // This route will ignore all throttling
@Get('health')
getHealth(): string {
return 'API is healthy!';
}
@Get('metrics')
getMetrics(): string {
return 'Application metrics data.'; // This route is throttled
}
}Beyond IP Address
By default, the NestJS Throttler module identifies clients by their IP address. However, for authenticated users, you might want to apply limits based on their user ID, rather than their IP.
This requires extending the ThrottlerGuard and overriding the getRequestResponse method to extract a different key (e.g., from a JWT token). This ensures that a single user cannot bypass limits by changing IPs.
Understanding Throttling
You've learned about rate limiting and throttling. Let's test your understanding!
Summary of Protection
Great job! In this lesson, you learned about the importance of rate limiting and throttling to protect your NestJS APIs. You explored how to set up the @nestjs/throttler module, configure global limits, apply route-specific rules, and even skip throttling for certain endpoints.
Implementing these techniques is a crucial step in building robust and secure backend services. Keep exploring how to fine-tune these limits and integrate them with other security measures!
Pertanyaan yang Sering Diajukan
Apakah pelajaran “Pembatasan Laju dan Throttling” gratis?
Ya — teks lengkap “Pembatasan Laju dan Throttling” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus NestJS Enterprise Backend APIs, upgrade ke CoddyKit PRO. Kursus NestJS Enterprise Backend APIs mencakup 3 pelajaran total.
Apa yang akan aku pelajari di “Pembatasan Laju dan Throttling”?
Terapkan pembatasan laju dan throttling untuk melindungi API dari penyalahgunaan serta memastikan penggunaan yang adil bagi semua klien. Kamu berlatih NestJS Enterprise Backend APIs dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.
Apakah aku perlu pengalaman untuk memulai NestJS Enterprise Backend APIs?
Tidak diperlukan pengalaman sebelumnya. NestJS Enterprise Backend APIs di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 1 dari 3.
Berapa lama pelajaran “Pembatasan Laju dan Throttling” memakan waktu?
Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.
Bisakah aku menulis dan menjalankan kode dalam pelajaran NestJS Enterprise Backend APIs ini?
Ya. Setiap pelajaran NestJS Enterprise Backend APIs menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.
Semua pelajaran dalam kursus ini
- Pembatasan Laju dan Throttling
- Pencatatan dengan Winston/Pino
- Pemantauan dengan Prometheus