ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Frameworks & web · #nestjs
The goal is to guarantee a reversible upgrade path when a NestJS major release alters decorator signatures or DI configuration, allowing teams to restore the pre‑upgrade state without losing uncommitted work. The nest update CLI speeds up dependency resolution to the latest compatible versions but provides no built‑in mechanism to revert transitive changes,
Goal: Verify that a NestJS service using TypeORM can resume normal operation after a database backup has been restored without processing requests that were in flight at the moment of the dump. Constraints: The backup is performed externally (e.g., pg_dump) and the application is restarted against the restored instance; TypeORM does not retain knowledge of t
The goal is to achieve zero‑downtime deployments while preserving the ability to roll back a schema change safely in a NestJS application that uses TypeORM. Two documented approaches exist: enabling the synchronize flag so TypeORM updates the schema automatically on startup, or generating explicit up/down migration scripts and running them via the NestJS/Typ
NestJS provides the CacheInterceptor to optimize response times by caching results based on a defined Time-To-Live (TTL). While this effectively reduces load for static or semi-static data, the default behavior triggers a cache miss immediately upon TTL expiration. In high-throughput environments, this creates a risk where multiple concurrent requests for th
Request Lifecycle Design When implementing access control in a NestJS application (v10+), there is a design choice between using Guards and Interceptors to handle authorization logic. While both can intercept incoming requests, they operate at different stages of the request pipeline. Constraints and Trade-offs Guards are executed before Interceptors and are
When building a NestJS application that relies on the injected HttpService for outbound HTTPS calls, I need to ensure that all requests use a specific DNS resolver (e.g., an internal DNS server) and optionally relax certificate validation for internal services with self‑signed certificates. The HttpService is a thin wrapper around Axios, which ultimately use
When building a NestJS API that serves large datasets, developers must decide how to paginate queries while respecting soft‑deleted records. Offset‑based pagination (limit/offset) is easy to add with QueryPipe and TypeORM’s findAndCount, but if the total count includes soft‑deleted rows, the number of active entities returned on a page can fall below the req
Goal: Safe Schema Rollback in NestJS Applications When evolving the database schema of a NestJS service, the ability to revert changes without data loss is a critical constraint. Two documented strategies exist: using TypeORM's migration down methods to programmatically reverse schema alterations, and employing external migration scripts (e.g., migrate-mongo
Goal: Achieve zero‑downtime migration of a small NestJS 9 application that uses the Express adapter and @nestjs/websockets by enabling graceful shutdown hooks so that in‑flight HTTP requests finish before the process exits. Uncertainty: While app.enableShutdownHooks() guarantees that HTTP handlers complete, it is unclear whether the same mechanism reliably t
mongoose