Building a Stateful Service for Large-Scale Chat TPS

Those who are listening to the original 1st lecture may feel a little confused.

In this existing structure

/network /network.go /socket.go

The structure has been changed as follows:

/network /network.go /server.go /socket.go /util.go

For the convenience of the lecture, I have built a basic skeleton in advance.

Rather than seeing it as an omission, it's something I just didn't pay attention to.

Please refer to the following sections and apply.

1. server.go

This is a Router that defines APIs.

Please refer to the section 이러면 Skelton 서버가 구축이 됩니다.

2. utils.go

There is a normalization function for the response.
처음 뵙는 분들! 이전 강의에 대한 소스코드를 간단하게 알려드릴게요. You can refer to the section.

We apologize for any inconvenience this may cause you while attending the lecture.

Hello, it's nice to meet you for part 2.

This course covers real-world deployments without any downtime.

Although we do not cover the FE part in depth, we do cover the BE part in depth.

The architecture used in this lecture is not correct.

This lecture was filmed with the hope that you will refer to the architecture I am introducing, think about better architectures, and ask questions.

Development isn't just about writing code.

I think it would be good if we could explore better directions and share our knowledge together.

Please ask many questions and I hope you have a good development!! 💕