+0
Daily
9,491
stars
2,856
forks
385
watchers
89
prs
98
issues
9
releases
README
📘Introduction |📽Video Demo | 🏖TODO LIST | 🌈Architecture |💡Flow Chart|🌁Quick Start|👨🏻✈️Built-in Commands|🎤Chat|❓QA|💌Contact 中文文档 V2.0 - [x] Upgrade to JDK17 & springboot3.0 - [x] Client SDK - [ ] Client use picocli instead of springboot. - [x] Support integration testing. - [ ] Integrate OpenTelemetry . - [ ] Support single node startup(Contains no components). - [ ] Third-party components support replacement(Redis/Zookeeper, etc.). - [ ] Support web client(websocket). - [x] Support docker container. - [ ] Support kubernetes operation. - [ ] Supports binary client(build with golang). Introduction CIM(CROSS-IM) is an IM (instant messaging) system for developers; it also provides some components to help developers build their own scalable IM. Using CIM, you can achieve the following requirements: - IM instant messaging system. - Message push middleware for APP. - Message middleware for IOT massive connection scenarios. If you have any questions during use or development, you can contact the author. Video Demo Click the links below to watch the video demo. | YouTube | Bilibili| | :------:| :------: | | Group Chat Private Chat | Group Chat Private Chat | | | !demo.gif TODO LIST [x] Group Chat [x] Private Chat [x] Built-in Commands [x] Chat History Query [x] AI Mode [x] Efficient encoding/decoding with Google Protocol Buffer [x] Flexible horizontal scaling based on actual needs [x] Server-side automatic removal of offline clients [x] Client automatic reconnection [x] Delayed Messages [x] SDK development package [ ] Group categorization [ ] Offline messages [ ] Message encryption Architecture ! - Each component in CIM is built using SpringBoot - Client build with cim-client-sdk - Use Netty to build the underlying communication. - MetaStore is used for registration and discovery of IM-server services. cim-server IM server is used to receive client connections, message forwarding, message push, etc. Support cluster deployment. cim-route Route server; used to process message routing, message forwarding, user login, user offline, and some operation tools (get the number of online users, etc.). cim-client IM client terminal, a command can be started and initiated to communicate with others (group chat, private chat). Flow Chart ! - Server register to MetaStore - Route subscribe MetaStore - Client login to Route - Route get Server info from MetaStore - Client open connection to Server - Client1 send message to Route - Route select Server and forward message to Server - Server push message to Client2 Quick Start Docker The allin1 image comes with Zookeeper, Redis, cim-server, and cim-forward-route pre-installed, all managed by Supervisor for an out-of-the-box experience. Supported platforms: linux/amd64, linux/arm64, linux/arm/v7 Port mapping: | Port | Service | Description | |------|---------|-------------| | 2181 | Zookeeper | Service registration & discovery | | 6379 | Redis | Data caching
Top issues
#10Mobile iOS Android 13 comments · 2019-01-03#65为什么server转发消息给目的client的时候要走netty而不是直接http调用呢11 comments · 2019-10-31#19其他组件启动都没有问题,就是client启动报错了11 comments · 2019-01-16#135Help wanted! Here are some simple tasks that can be handled🎉.10 comments · 2024-07-26#56netty 路由发消息通过http服务实现,性能怎么样6 comments · 2019-09-20#117数据是如何存储的呢?5 comments · 2021-03-17#97为什么发送消息走http5 comments · 2020-06-14#24画了个简易的实现原理图 ^_^5 comments · 2019-01-18
Latest release
v2.1.0 v2.1.0 2025-06-09What's Changed Upgrade to protocol3 by @crossoverJie in https://github.com/crossoverJie/cim/pull/163 Protocol add properties by @crossoverJie in https://github.com/crossoverJie/cim/pull/164 [fix] Cross-platform compilation by @chenqwwq in https://github.com/crossoverJie/cim/pull/165 feat: Support allin1 docker image by @crossoverJie in https://github.com/crossoverJie/cim/pull/169 feat: Enhance messaging system with batch message support by @crossoverJie in https://github.com/crossoverJie/cim/pull/171 Feat/offline msg by @Zdanquxunhuan in https://github.com/crossoverJie/cim/pull/170