NestJs Questions

HttpException must be caught by custom exception filters, while custom exceptions are handled automatically.

HttpException is deprecated and should always be replaced with custom exception classes.

There is no practical difference; both can be used interchangeably for error handling.

HttpException is used for generic HTTP errors, while custom exceptions represent specific business logic errors.

A representation of a database connection

A method for handling HTTP requests

A configuration file for a NestJS application

A definition of the structure and data types for documents in a collection

To define database tables

To handle user authentication

To provide methods for interacting with a specific entity

To manage database migrations

By using the @Catch() decorator on the global filter class.

By using the useGlobalFilters() method in the main.ts file.

By adding the global filter class to the providers array in the module definition.

By extending the base ExceptionFilter class and annotating it with the @Global() decorator.

Integration Testing

Unit Testing

End-to-End (E2E) Testing

Regression Testing

To validate the data type of an input parameter.

To convert a string value to a Boolean.

To transform a numeric string into an integer.

To parse an object into a JSON string.

Manually updating configuration files

Using a service registry (e.g., Consul, etcd)

Relying on client-side load balancing

Hardcoding service addresses

@nestjs/microservices

@nestjs/common

@nestjs/core

@nestjs/platform-express

Improved performance for handling a large volume of events

Enhanced type safety when defining event listeners

Centralized management and organization of event listeners

Automatic retry mechanisms for failed event handlers

context.switchToHttp().getResponse()

context.getRequest()

context.switchToWs().getClient()

context.getNext()