Building a Chat Platform Using Spring Boot

The lecture itself was good because it could be watched in 3~4 days even if you invested a lot of time. If you watch it quickly, you can probably watch it in about a day. The lecture content is about creating a simple provider for authentication and processing it, and although it is not the main content, I was able to briefly learn about the jwt authentication method. Regarding chat, he explained the pub sub model, and he explained method A and a little about B. He told me about how to find it myself and do it, like an open ending? As I continued to work, I realized that in practice, there are many times when I spend a lot of time on really ridiculous things. Especially when it comes to error handling. The lecture goes by quickly, but the instructor often makes mistakes. For example, when creating a usercredential entity, declaring the table name as "user", or using a different name for the mapping method, causing a 404 error on the front. create_at -> The part that needs to be declared as created_at When a problem occurs, I liked the part where you can find and solve it yourself before watching the lecture on solving errors, and it also feels a bit practical. ㅎㅎ Beginners may wonder why it doesn't work. And this is not a lecture that says you can service a chat application after watching one lecture. I want to complete a complete chat service. !

It was good that it covered several parts together rather than just one topic. I liked the part that covered JPA and JWT Token in detail, and the part that showed why IO is reduced in wss communication compared to general HTTP by analyzing actual requests was impressive. Thank you for the great lecture. :)

It is a lecture that provides a good amount of content to view in a day and delivers it in a clean manner.

I watched it very well and it was very helpful. I would appreciate it if you could create an intermediate or higher level course that covers stomp in more depth (adding/deleting sessions, web socket interface, etc.) or covers design that meets non-functional requirements at the actual production level, although the criteria are vague.

I tried to apply it to my current side project. As someone who has only worked on the backend, I understand the code and the ws communication of connecting to ws using WebSocket and STOMP and exchanging chat messages, but I was very confused when I connected to the actual front end by simply turning on port 3000 without setting up a file. I couldn't load package.json in WebStorm, so I just created a new project and copied and pasted all the files in the client package, but I had various dependency issues, react version issues, createContext issues, etc. As someone who has only worked on the backend, I have no idea how to turn on the port 3000 server.... As a backend developer, I learned how to use clean Swagger annotations and the WebSocket - STOMP for chat. I haven't tried the chat yet....

I am a junior who uses Spring in my work. I took the course because I was curious about the lecture, and it was good because I could learn both HTTP and Socket communication. In the case of HTTP, everyone uses it, and I know JPA to some extent?? So I took the course with the idea of reviewing it. I didn't deal with Socket, but I was able to briefly understand why it should be used, in what situations it is efficient, and why it is efficient. I was also able to implement a simple implementation accordingly. Rather than feeling like the lecture taught me everything, I felt like it showed me the right path. It felt like it taught me what development methods and what I should study for development. Thank you for the great lecture.

There is also information about web sockets, but I think there is a lot of useful information. I enjoyed seeing the scenes where you directly disassemble JWT and debug projects together without embellishment, etc. Thank you.

I was thinking of learning about WebSockets, which are similar to regular Webs, and this was a great opportunity. Great content. Thank you.