Im implemented with Netty, Vue+element-ui

Before working in contact with a few open-source IM products, coupled with the use of Netty to achieve a few services, so there is the idea of using Netty to implement an IM, so in my spare time to write an IM, and like Netty of the program members to share.

In view of the convenience of extension, in the service side of the http+socket combination of design, the client all the requests are based on HTTP, such as sending messages, modify personal information, all of the message is pushed to the client by the socket, so that the design can be in the case of large concurrent traffic, Deploy the good HTTP service separately from the socket service.

The HTTP service is also based on the Netty implementation, extending on top of Netty, referencing the spring MVC annotations for Netty-rest-server (netty-rest-server), which enables annotations to be injected into the rest controller To implement unified exception handling controllers and interceptors (such as cross-domain interceptors, authentication interceptors, and so on).

The decoupling and communication between the HTTP service and the Scoket service can be implemented using either a Java built-in queue or a Redis publish/subscribe implementation, and after the message processor receives the task, it is processed by the thread pool, processed and sent to broadcast via Groupchannel or to the specified channel.

The front-end is based on Vue+element-ui, and it is recommended to use the Chrome browser experience.

Online experience

Test users: Test1, test2, test3, passwords are: 123456

Source Address

• Service side
• Web-side

Im implemented with Netty, Vue+element-ui