Menu

#Nestjs

66 posts

Feed·
20 of 66 posts
Graceful Shutdown in Node.js and NestJS on Docker: SIGTERM, Draining, and Hook Order — Field Notes
📰
0Read More

Graceful Shutdown in Node.js and NestJS on Docker: SIGTERM, Draining, and Hook Order — Field Notes

DEV Community: docker·Ahmed Mahmoud·about 9 hours ago
#sZXWkCV2
#devtodocker#devto#dev#node#process

Headline: A graceful shutdown means a Node.js process that receives SIGTERM stops taking new work,...

15s
A NestJS-like framework for Python: why I built Austial on FastAPI
🖼️
0Read More

A NestJS-like framework for Python: why I built Austial on FastAPI

DEV Community: fastapi·Austial·5 days ago
#RzGB4Lr7
#devtofastapi#devto#dev#nestjs#fastapi

If you are looking for a NestJS-like framework for Python, this is the one I built. NestJS gives a...

15s
How to Build an MCP Server in NestJS: Streamable HTTP, Guards and DI (Tested)
🖼️
0Read More

How to Build an MCP Server in NestJS: Streamable HTTP, Guards and DI (Tested)

DEV Community: nestjs·Waseem Anjum·11 days ago
#goJbYK47
#devtonestjs#devto#dev#nestjs#import

Build an MCP server in NestJS 12 with the official MCP SDK: Streamable HTTP controller, auth guard, DI in tools, per-token scopes and 5 tested gotchas.

15s
NestJS vs Hono vs Fastify (2026): Benchmarked on Node.js 26
🖼️
0Read More

NestJS vs Hono vs Fastify (2026): Benchmarked on Node.js 26

DEV Community: nestjs·Waseem Anjum·11 days ago
#JyB7fSuW
#devtonestjs#devto#dev#fastify#nestjs

NestJS vs Hono vs Fastify vs Express benchmarked on Node.js 26: requests per second, startup time and memory on one core, plus which to pick for your API.

15s
NestJS Rate Limiting: In-Memory vs Redis vs Postgres
🖼️
0Read More

NestJS Rate Limiting: In-Memory vs Redis vs Postgres

DEV Community: security·Waseem Anjum·12 days ago
#xROzjvFT
#devtosecurity#devto#dev#redis#storage

I benchmarked @nestjs/throttler with in-memory, Redis and Postgres storages: latency, 429 correctness, and what breaks with two Nest instances.

15s
BullMQ in NestJS: Retries, Idempotency and Dead-Letter Queues
📰
0Read More

BullMQ in NestJS: Retries, Idempotency and Dead-Letter Queues

DEV Community: redis·MUHAMMAD ZAIN UL ABIDIN·12 days ago
#5hw7jRuP
#devtoredis#devto#dev#queue#bullmq

Blind retries double-send emails and double-charge customers. The BullMQ setup I run in NestJS: jittered backoff, idempotent jobs, and a dead-letter queue.

15s
High-Concurrency Distributed Rate Limiter for Node.js & NestJS with Redis
🖼️
0Read More

High-Concurrency Distributed Rate Limiter for Node.js & NestJS with Redis

DEV Community: redis·Tarek Mohamed·17 days ago
#3MBuAVMc
#devtoredis#devto#dev#rate#distributed

A high-concurrency sliding-window distributed rate limiter middleware for Express and NestJS backends powered by atomic Redis Lua scripts.

15s
0Read More

Every refactor in our NestJS repo turns into fixing u/Traced decorators

Reddit r/typescript·u/Hour-Librarian3622·18 days ago
#1o6xsz4H
#every#traced#decorator#refactor#nestjs

NestJS monorepo, eleven services. Two years ago we wrote a `@Traced()` decorator that wraps every service method in an OpenTelemetry span, plus a typed helper so attribute names come from one union type and nobody writes `userId` in one place and…

15s
Prisma Generator NestJS DTO — pluggable DTOs with annotations and custom generators
🖼️
0Read More

Prisma Generator NestJS DTO — pluggable DTOs with annotations and custom generators

DEV Community: nestjs·Tommaso Meli·6 months ago
#F0lLYpFH
#dev#afterall#prisma#nestjs#generator

If you build NestJS APIs on top of Prisma, you've probably felt the friction: your schema is the...

15s
Claude Wrote a NestJS Service. TypeScript Was Happy. ESLint Found 6 Security Holes.
🖼️
0Read More

Claude Wrote a NestJS Service. TypeScript Was Happy. ESLint Found 6 Security Holes.

DEV Community: devsecops·Ofri Peretz·6 months ago
#OEXrPxJ3
#dev#nestjs#security#class#article

I gave Claude one prompt and got 200 lines of correct NestJS. TypeScript compiled clean. Then I ran eslint-plugin-nestjs-security. 6 errors, 3 seconds. Here is what it found and why each one is an AI failure mode.

15s