Slack Clone Coding [Backend with NestJS + TypeORM]
Let's learn NestJS, which is called the Spring of Node.js, and experience the convenience of Dependency Injection. Let's learn everything from API development, comparison with Express, deployment, and testing.
I created a chat app with my own hands, and even developed a server! Meet NestJS, the hottest thing these days.
In Express With NestJS !
I was originally using Express as a server framework and Sequelize as a DB at work. But I saw a lot of mention of NestJS in the community, so I tried it out and... My eyes are wide open👀! After that , we converted all company services to NestJS, and also converted Sequelize to TypeORM.
Spring of the node system, Hot NestJS 🔥
NestJS, called the Spring of Node.js! It is said that even developers who left Node to do Spring are coming back because of NestJS. How is NestJS different from Express, which has been widely used so far, and how powerful is it? In this lecture, we will introduce the functions of NestJS. We will convert the web server built with Express to NestJS, and directly create the backend part of a web app similar to Slack.
Well then, let’s learn first-hand why NestJS is so hot.
I recommend this to these people!
For those who want to get started with Node.js server development with NestJS
For those who feel that Express features are lacking and are looking for alternatives
Anyone who wants to implement the backend part through clone coding
Zero second slackclone coding , Backend concerns completely resolved!
We're going to build the backend part of a web app similar to Slack.
We will introduce the features of NestJS and try converting Express server to NestJS.
You will learn how to move away from Express and understand the benefits of NestJS, and be able to build a NestJS server.
Immediately applicable in practice!
I will share tips I learned while using NestJS for a year at my company, such as how to read the official NestJS documentation, how to draw ERD, and how to create API documentation.
As a bonus, it even works OK with websockets and testing!
Please check before taking the class!
This lecture is the backend part of the [Slack Clone Coding] lecture. However, you can take this lecture without taking the previous frontend part. If you are curious about how to create a frontend,Please check the previous lecture .
Learn these skills.
NestJS
TypeORM
Socket.io
Node.js
Let's make it ourselves!
Slack Clone Coding - Backend Part Development
Request validation and response standardization
Automatically generate Swagger documentation via NestJS
As well as the NestJS + TypeORM source code, We also provide the corresponding Express + Sequelize source code for the code .
#2 Quickly answer the question I will answer you.
The great thing about my course is the Q&A. If you have a question, I will answer it within a day. Please study actively by freely asking questions about course-related content. It will help you understand the content better!
Q. Slack Clone Coding - [Real-time Chat with React!] Do I need to take the course as well? I'm not interested in the front end.
If you are only interested in server development, you only need to take this course. However, when coding the backend, you need a frontend to send a request to the backend, right? That's why I've completed the frontend code. You just need to run the frontend code. Use the frontend screen to send a request to the backend.
Q. Do I need to know Express? I want to skip Express and just use NestJS.
The lectures often introduce Express or compare its differences with Express. You should be able to read some Express code to take the course smoothly. Since NestJS uses Express internally, it is recommended to understand Express.
Please note before taking the class!
Nest.js uses version 8. It would be smoother to take the course using version 7 or 8.
Curious about other clone lectures? 22 hour Twitter clone!
Recommended for these people
Who is this course right for?
Anyone who wants to get started with Node.js server programming using NestJS
If you are trying to switch from Express to NestJS
If you are familiar with Spring and are looking for something similar in Node
Need to know before starting?
Node.js Basics
Experience with Express, Passport, Sequelize
Typescript Basics
Hello This is
65,692
Learners
1,619
Reviews
9,708
Answers
4.8
Rating
22
Courses
제 강의의 장점은 Q&A입니다(인프런 답변왕 2회 수상). 24시간 이내에 최대한 답변드립니다! 같이 고민한다는 느낌으로 답변 드릴게요!
One of the key strengths of my courses is the Q&A support. (Winner of the Inflearn Q&A King award twice) I respond to your questions within 24 hours, doing my best to help you out! You’ll feel like we’re solving the problems together.
👉ZeroCho Lectures 제로초 강의 전체 로드맵. A complete roadmap of all my courses is available here.
– Node.js교과서, 코딩자율학습 제로초의 자바스크립트, Let's Get IT 자바스크립트, 타입스크립트 교과서 저자 – ZeroCho.com 운영자 – 현) 유튜브에서 ZeroCho TV로 개발 관련 방송중 – 현) 스모어톡 CTO – 전) 오늘의픽업 CTO(카카오모빌리티에 엑싯 후 카카오모빌리티 최연소 개발파트장)
Author of Node.js Textbook, Self-Guided JavaScript by ZeroCho, Let's Get IT JavaScript, and TypeScript Textbook
The technology stack that I want to learn is mainly covered by Zerocho, so I signed up for almost all of the lectures, but the lecture-style on YouTube doesn't seem to suit me. Should I say it's chaotic and distracting? It feels more like he's commentating while playing Starcraft than teaching in a straightforward manner?? He just mentions things and passes them over, and I keep thinking that I'll look them up later... Before the lecture starts, he says, "What will I explain today?", and then he organizes them and tells me. If you can't follow along, this is the final version of today's lecture. I think this kind of lecture suits me. The content is not bad. Honestly, I hesitated to leave a review even after attending so many lectures because I felt burdened by leaving a bad review, but since I paid for the lecture, I'll leave my honest opinion. I'll watch the old lectures and leave as many reviews as possible. Lastly, he answers questions very well. He has recorded many lectures, and some of them are quite old, but I think it's really great that he maintains them while answering questions! I hope you'll continue to give us great lectures in the future.
There is a part in the middle that shows migration from express to nestjs, but it is not easy to follow this part for someone who has not taken the existing lecture. There is also the DB table creation and a webpack error that suddenly appears... I think you should make a lecture for people who have not taken the express lecture...
It was good, but I haven't seen the previous lectures, and although it's unrelated to the previous lectures, I think there are too many examples from those lectures, so I think that part is a little difficult.
I liked the part where you explained the differences with Express. I was impressed by how you had a lot to say and how you tried to teach as much as possible.
However, I wish you were a little more friendly. I saw the answer to another person's question, and it seems like the person asking the question has to be careful. I think it's a bit strange to tell people to think about their questions and not just follow along without thinking.
The instructor is good, so that may be the case, but I hope you don't forget that most of the people watching this lecture are beginners in NestJS. I'm enjoying the lecture.
Thank you for your opinion. However, my opinion has not changed. I think there are two types of students. One type is those who really want to study, and the other type is those who just follow along and get results. I want only those who really want to study to take my class, even if it means making less money. That is why I do not accept questions like, “No, you can’t follow along.” I do not want to hear people say that my lectures were not helpful.
It seems that many people are still not proficient in nestjs. When showing test code, it seems that they do not know well when to use useValue, useClass, and useFactory, as stated in the official documentation. Also, the lecture video is not well organized. It was edited from a live broadcast and produced as a lecture video, but the lecture video itself is not organized and sometimes contains incorrect explanations. Of course, the incorrect parts are explained in subtitles or supplementary videos, but I think that is not good in itself. It felt like they were not proficient enough in the framework to film a paid lecture on nestjs.
I'm sorry. There were a lot of shortcomings at that time, so I plan to re-shoot based on the manuscript I'm writing for this book. I'll do it in a format where I analyze the internal implementation.