쉐도잉 연습: Every NestJS Concept Explained in 9 Minutes - YouTube로 영어 말하기 배우기

C2
쉐도잉 컨트롤
0% 완료 (0/87 문장)
I know exactly which button to press on my microwave to heat up my food, but if it breaks, I wouldn't be able to fix it.
⏸ 일시 정지
모든 문장
87 문장
1
I know exactly which button to press on my microwave to heat up my food, but if it breaks, I wouldn't be able to fix it.
2
So the same goes for programming.
3
So have you ever wondered how some people seem to always know how to fix the code, where to find the relevant information, and how to best implement new features?
4
They don't actually know everything.
5
They just understand the key concepts and principles that allow them to navigate any piece of code they encounter.
6
And after countless hours of going through the NestJS documentation, I've condensed the entire framework into 10 core concepts.
7
And by the end of this video, I'm fairly confident that you too will be able to understand any NestJS code you encounter.
8
The first concept is not often talked about, but it's actually a key to understand what NestJS is and what you can build with it.
9
So there is a misconception that NestJS is only for building APIs.
10
but in fact, there are three types of applications you can build with Nest.
11
You can create HTTP server using the Nest Factory Create and request endpoints and effectively create APIs and web servers.
12
But you can also create microservices applications using Nest Factory Create Microservice.
13
And microservices are very similar to HTTP servers, except that they can use different transport protocol such as TCP or NAT, and they can communicate via an internal network.
14
And last but not least, you can also create standalone applications using Nest Factory Create Application Context.
15
And a standalone application is just an application that doesn't have network listener.
16
So they are great for creating scheduled tasks or creating CLI tools even if you want.
17
But they all have one thing in common.
18
They need a root module.
19
So let's talk about modules now.
20
Modules are the building blocks of a Nest application.
21
So you can picture a Nest app as a graph made of modules.
22
And at the top, you always have a root module, and that root module can use other modules, and those modules can themselves use other modules and so on.
23
For example, you could have an application with a product module, an order module that uses a cart and payment module, and they could all be using a shared configuration module.
24
In terms of the implementation, a module is a class that is annotated with a module decorator.
25
And you absolutely need to understand the concept of decorators because they are everywhere in NestJS.
26
Decorators can be a bit strange to start with, but once you understand what they are, it all clicks and you can do really powerful things.
27
So a decorator is a special kind of function and it can be attached to methods, classes, properties, and it modifies their behavior and it can even add metadata.
28
Think of decorators as wearing accessories or suits that give you extra power.
29
For example, you can take an empty naked class and dress it with a fancy shiny module decorator suit.
30
And that means that it can be used by other classes that are wearing the same shiny module decorator suit.
31
To create the application module graph, you define relationship between modules by passing an object property to the module decorators.
32
And you define the related modules in the import property.
33
And once you have modules, you can add controllers inside them.
34
Controllers are classes that are annotated with the controller decorator.
35
So let's say that they are wearing a blue jacket.
36
So a controller is simply in charge of receiving incoming requests and returning a response.
37
So you can define a root path in the controller decorator, and you add methods to handle the incoming request.
38
and those methods can be annotated with a HTTP verb and those decorators can take a sub root as parameter.
39
So the main role of the controller is to receive requests and return response.
40
Anything else is delegated to other classes.
41
Most of the code that you will be writing in Nest is within providers.
42
So a provider is simply a class that can be injected in other classes as dependency.
43
So let's take a user service class as an example.
44
So you annotate that class with the injectable decorator to indicate that it's a provider.
45
Then you declare it as a provider in the user's module.
46
And now you can inject it in the controller via the constructor so you can think of providers as
47
freelance workers and nest.js is an agency that places those freelance workers wherever they are needed and congratulations you've
48
used dependency injection and the singleton pattern now let me show you how to take full control of the request handling flow starting wheel middlewares.
49
When you want to take a plane, you don't just park on the tarmac and enter the plane.
50
So you have to go to check in your luggage, then you go through security, then you might even go through border control, then you show your boarding pass, and finally you get on the plane.
51
So just like a plane passenger, you can make a request go through several stages before it's handed over to the method handler.
52
So for example, you could use middleware to log every incoming requests.
53
But don't start adding middlewares everywhere because I'll show you in the next concept that Nest comes with built-in features for common request flow management.
54
Guards are a critical part of the request lifecycle in NestJS.
55
So they work more or less like security check at an airport and their primary purpose is to determine whether the request will be handled by the root handler based on specific conditions like roles, permissions, or any custom logic.
56
So they They have access to the execution context, and that allows them to inspect some details about the request.
57
For example, an authentication guard can check if the user is authenticated and authorized to access a requested resource.
58
And if the guard returns true, then the request passes through.
59
And if it returns false, then the request is denied, and we'd send an error response to the client, for example.
60
After the guard, you can add interceptors to your application.
61
So they run before and after the root handler.
62
So they give you full control over the request response cycle.
63
So interceptors implement the nest interceptor interface and they can perform tasks like logging or caching.
64
For example, an interceptor can log request details or map the response and input data format.
65
The next stop before getting to the handler is pipes.
66
So that's where you can validate and transform the data that is handed to the handler to ensure that it meets certain criteria or is in the correct format.
67
So pipes are classes that implement the pipe transform interface and they are annotated with the injectable decorator.
68
So for instance, a pipe can validate the data sent in the request to ensure that it conforms with the expected format or the expected type or certain constraints.
69
It's up to you to implement whatever validation rules you want.
70
But if the data is invalid, then the pipe can throw an exception, preventing the root handler from executing.
71
Additionally, pipes can transform the data into a more suitable format for processing.
72
For example, a pipe can convert a string input into integer or parse dates from string representations.
73
So built-in pipes like validation pipe, parsing pipe, and parse UUID offer some common validation and transformation.
74
but you can also create custom pipes to handle specific requirements.
75
If at any point during the request handling, there is an unhandled error, Nest.js would return a 500 internal error by default.
76
But you can manually throw standard HTTP exceptions as well and be a bit more descriptive.
77
And you can even customize error handling through exception filters.
78
Exception filters are classes that implement the exception filter interface and they are decorated with the catch decorator.
79
They can catch exceptions thrown by any part of the request handling process, including guards, interceptors, pipes, or root handlers, of course.
80
But when an exception is caught, the filter determines how to handle it and what response to send.
81
For example, you can have like a global exception filter that can catch all exceptions, log the error details and return a standard error response to the client.
82
So this ensures that the client receives consistent error messages and that sensitive information is not exposed.
83
And that will make front-end developers very happy as well.
84
So exception filters provide a centralized way of handling errors and maintain the stability and security of your application.
85
Everything that I've just shown you needs to be applied if you want these concepts to stick.
86
You can watch this next video and apply those concepts, and you can follow along as I build a podcast API from scratch.
87
And in that video, I'll also show you how to test your app.
App Store 및 Google Play에서 4.9/5

Shadowing English 모바일에서

Shadowing English 앱으로 언제 어디서나 영어를 배우세요. 오늘 의사 소통 능력을 향상 시키십시오!

학습 진행 상황 추적
AI 채점 및 오류 수정
풍부한 비디오 라이브러리
Shadowing English Mobile App

이 수업에 대해

이번 수업에서는 NestJS의 핵심 개념을 배우며, 이를 통해 프로그래밍에서의 문제 해결 능력을 향상시킬 것입니다. 프로그래밍이란 단순히 코드를 작성하는 것이 아닌, 이를 이해하고 수정하는 능력이 필요합니다. 이 수업을 통해 여러분은 NestJS를 활용하여 다양한 유형의 애플리케이션을 개발할 수 있도록 준비할 것입니다. 이를 위해 각 개념을 이해하고, 실제 상황에서 어떻게 적용할 수 있는지를 연습합니다.

주요 어휘 및 구문

  • 모듈 (Module): Nest 애플리케이션의 구성 요소로, 여러 기능을 구현하는 데 사용됩니다.
  • 디코레이터 (Decorator): 클래스나 메소드의 행동을 수정하거나 메타데이터를 추가하는 특별한 함수입니다.
  • 컨트롤러 (Controller): 요청을 수신하고 응답을 반환하는 역할을 하는 클래스입니다.
  • 프로바이더 (Provider): 다른 클래스에 주입될 수 있는 클래스로, 의존성 주입을 가능하게 합니다.
  • 미들웨어 (Middleware): 요청 처리 흐름을 제어하는 역할을 하는 요소입니다.
  • 마이크로서비스 (Microservice): 서로 다른 프로토콜을 사용하는 독립적인 서비스입니다.
  • HTTP 서버 (HTTP Server): 웹 요청을 처리하는 서버입니다.
  • 독립 실행형 애플리케이션 (Standalone Application): 네트워크 리스너가 없는 애플리케이션입니다.

연습 팁

이 영상을 통해 습득한 내용을 효과적으로 연습하고 싶다면, shadowspeakshadow speech 기법을 사용하세요. 각 개념을 설명하는 속도에 맞춰 따라 해보세요. 처음에는 속도를 조금 느리게 하여 발음에 집중하고, 점차 원래 속도로 돌아가 연습해보세요. 또한, 영어 발음 교정을 위해 반복해서 소리내어 읽는 것도 좋은 방법입니다. 각 개념의 설명을 주의 깊게 듣고, 발음을 개선하며 IELTS 스피킹 등의 테스트를 준비하는 데에도 도움이 될 것입니다. 여러분의 말하기 능력을 향상시키기 위한 이 연습이, 자신감을 높이고 다양한 프로그래밍 문제에 효과적으로 대응하는 데 도움이 될 것입니다.

쉐도잉이란? 영어 실력을 빠르게 키우는 과학적 방법

쉐도잉(Shadowing)은 원래 전문 통역사 훈련을 위해 개발된 언어 학습 기법으로, 다언어 학자인 Dr. Alexander Arguelles에 의해 대중화된 방법입니다. 핵심 원리는 간단하지만 매우 강력합니다: 원어민의 영어를 들으면서 1~2초의 짧은 지연으로 즉시 소리 내어 따라 말하는 것——마치 '그림자(shadow)'처럼 화자를 따라가는 것입니다. 문법 공부나 수동적인 청취와 달리, 쉐도잉은 뇌와 입 근육이 동시에 실시간으로 영어를 처리하고 재현하도록 훈련합니다. 연구에 따르면 이 방법은 발음 정확도, 억양, 리듬, 연음, 청취력, 말하기 유창성을 크게 향상시킵니다. IELTS 스피킹 준비와 자연스러운 영어 소통을 원하는 분들에게 특히 효과적입니다.

커피 한 잔 사주기