OpenIM isn't just an open-source instant messaging component, it's an integral part of your application ecosystem. Check out this diagram to understand how AppServer, AppClient, OpenIMServer, and OpenIMSDK interact.
OpenIMSDK seamlessly integrates into your application, delivering a rich, real-time messaging experience without requiring intricate UI integration. It provides:
- Local Storage: For quick data retrieval and message synchronization.
- Listener Callbacks: Ensuring real-time message interactivity.
- API Encapsulation: Streamlining development processes.
- Connection Management: Guaranteeing reliable message delivery.
It's crafted in Golang and supports cross-platform deployment, ensuring a coherent messaging experience across all platforms.
OpenIMServer, meticulously developed in Golang, ensures a stellar instant messaging server capability with a multifold approach:
- Modular Composition: It's comprised of several modules, such as the gateway and multiple RPC services, offering a versatile messaging environment.
- Microservices Architecture: Supporting cluster modes, it assures outstanding performance and scalability to manage communication effectively across various instances.
- Diverse Deployment Options: Adapts to your operational preferences, offering deployment via source code, Kubernetes, or Docker.
- REST API: OpenIMServer provides REST API for business systems, aiming to empower your operations with additional functionalities like group creation and message push via backend interfaces.
- Callbacks: To expand its utility across varied business forms, OpenIMServer offers callback capabilities. That is, it sends a request to the business server before or after an event occurs, such as sending a message, enriching the interaction and data exchange flow in the communication processes.
You can quickly learn OpenIM engineering solutions, all it takes is one simple command:
$ make demo🤲 In order to facilitate the user experience, we have provided a variety of deployment solutions, you can choose your own deployment method according to the list below:
OpenIM Our goal is to build a top-level open source community. We have a set of standards, in the Community repository.
If you'd like to contribute to this Open-IM-Server repository, please read our contributor documentation.
Before you start, please make sure your changes are in demand. The best for that is to create a new discussion OR Slack Communication, or if you find an issue, report it first.
- Code Standards
- Docker Images Standards
- Directory Standards
- Commit Standards
- Versioning Standards
- Interface Standards
- Log Standards
- Error Code Standards
- OpenIM configuration and environment variable Settings
We want anyone to get involved in our community and contributing code, we offer gifts and rewards, and we welcome you to join us every Thursday night.
Our conference is in the OpenIM Slack 🎯, then you can search the Open-IM-Server pipeline to join
We take notes of each biweekly meeting in GitHub discussions, Our historical meeting notes, as well as replays of the meetings are available at Google Docs 📑.
Check out our user case studies page for a list of the project users. Don't hesitate to leave a 📝comment and share your use case.
OpenIM is licensed under the Apache 2.0 license. See LICENSE for the full license text.
The OpenIM logo, including its variations and animated versions, displayed in this repository OpenIM under the assets/logo and assets/logo-gif directories, are protected by copyright laws.