Turms is the most advanced open-source instant messaging engine for 100K~10M concurrent users in the world. Please refer to Turms Documentation (no English version for now) for details.
(Version of demo servers: ghcr.io/turms-im/turms-admin:latest, ghcr.io/turms-im/turms-gateway:latest, ghcr.io/turms-im/turms-service:latest)
-
turms-admin: http://playground.turms.im:6510
Both the account and the password are:
guest. (The account is allowed to query and add data, but is not allowed to update and delete data.) -
turms-gateway: http://playground.turms.im:10510 (port for WebSocket access) and http://playground.turms.im:11510 (port for TCP access)
-
turms-service (Admin API in dev environment with fake data supported): http://playground.turms.im:8510
-
Prometheus: http://playground.turms.im:9090; Grafana: http://playground.turms.im:3000
You can use any turms-client-(java/js/swift) implementation to send requests to turms-gateway and interact with other users.
In addition, Playground is set up automatically by just one command: ENV=dev,demo docker-compose -f docker-compose.standalone.yml --profile monitoring up --force-recreate -d
Running the following commands to setup a minimum viable cluster (including turms-gateway, turms-service and turms-admin) and its dependent servers (MongoDB sharded cluster and Redis) automatically:
git clone --depth 1 https://github.com/turms-im/turms.git
cd turms
docker plugin install grafana/loki-docker-driver:latest --alias loki --grant-all-permissions
docker-compose -f docker-compose.standalone.yml up --force-recreateAfter the cluster is set up, you can visit turms-admin at http://localhost:6510, and enter the account and password (turms by default). If you log in successfully, it means that the cluster of Turms has been setup successfully.
You can also apply the Terraform modules provided by Turms to quickly purchase cloud services and set up a turms cluster (uses spot instances by default). After running terraform apply, wait for about 3~15 minutes (Alibaba Cloud ECS is slow to pull ghcr images), and then visit http://<public IP>:6510, if you can access turms-admin, it means that the turms cluster has been set up successfully.
（Note: The following commands will automatically purchase cloud services and deduct the corresponding fees from your account）
git clone --depth 1 https://github.com/turms-im/turms.git
cd turms/terraform/alicloud/playground
export ALICLOUD_ACCESS_KEY=<your_access_key>
export ALICLOUD_SECRET_KEY=<your_secret_key>
terraform init
terraform applyThe architecture of Turms depends on the fanout read design for creating inboxes (or message timelines), and Turms supports push model, pull model, and push-pull model to be aware of the changes of business data (For details, Business Data Change Awareness). Most of the other design details also come from commercial IM projects.
And compared to many projects with obsolete technology stacks, Turms is also the only open source IM solution that is based on modern architecture and modern technology and is suitable for medium to large scale applications.
In addition, architecture design is an art of trade-off. Some IM products take rich features as their slogan at the cost of no support for medium to large scale applications (they are only suitable for team communications). However, Turms takes extreme performance as the first priority and supports complete (rather than rich) IM features to support medium and large-scale applications. Please refer to Turms Schema Design and Observability for details.
When you need to compare Turms with other open source IM projects for features, you can first compare Turms with other open source IM projects based on the following features of Turms. Usually, you can find the differences between professional IM projects and amateur IM projects. In addition, under the chapter of Product Comparison, we also mentioned the shortcomings of the Turms project for your reference.
Note: The main disadvantage of the current Turms project is that it does not provide support for living/chat room. The technical implementation of the living/chat room is not difficult, but the product requirements, quality attribute requirements, and restrictive conditions are quite different from the scenarios of general social applications, so the first version of Turms does not provide support for it. In addition, Turms is also not suitable for small-scale enterprise communication scenarios. Using Turms for enterprise communication scenarios is using a sledgehammer to crack a nut, because enterprise communication emphasizes feature-rich rather than extreme performance, which is inconsistent with the goals of Turms, so their designs are also different. If you want to support enterprise communication scenarios, you need to develop based on Turms yourselves.
- Support a complete set of IM features. Turms supports almost all IM features supported by commercial instant messaging products and no restrictions on business features. And Turms also supports advanced features such as unwanted words filtering (using Aho-Corasick automaton with double array trie) and tiered storage for messages.
- (Extensibility) Turms supports two approaches to extend: configuration properties and custom plugins. Of course, you can also modify the source code. For example, the plugin turms-plugin-minio based on turms-plugin is used to interact with MinIO server.
- (Flexibility) Turms provides hundreds of configuration properties for developers to meet various requirements. And most of the properties can be updated at the cluster level when the cluster is running without performance loss.
- (Agility) Support updating Turms servers without the users' awareness of shutdown to support rapid iteration
- (Scalability) The Turms server is stateless to be scaled out; Support multi-active across data centers
- (Deployability) Support container deployment to facilitate integration (CI/CD) with cloud services. Turms provides three solutions for container deployment out of the box: docker image, docker-compose script, and Terraform module
- (Observability) Support relatively complete features of observability for business analysis and troubleshoot
- (Scalability) Support medium to large scale instant messaging applications, and there is no need to refactor even if the application becomes large from medium-scale (There is still a lot of optimization work to be done for large applications, but Turms servers are easy to upgrade)
- (Security) Support API throttling and global user/IP blocklist to resist most CC attacks
- (Simplicity) The Turms architecture is lightweight, which makes Turms easy to learn and redevelop. Please refer to Turms Architecture Design for details)
- Turms depends on the MongoDB sharded cluster to support request routing (such as read-write separation) and tiered storage for medium to large scale applications
-
Observable system (Please refer to Observability for details)
-
Log (for events): Turms provides three types of logs: monitoring log, business log, and statistics log
-
Metrics (for aggregable data). It reflects the real-time status of the system and business data
-
Tracing
Note that the Turms server will provide more monitoring features that can be implemented efficiently as much as possible, but will not provide some common features that have a great impact on performance and are more suitable for third-party services to provide (such as DAU). For this kind of extended feature, you can implement them by offline or real-time analysis of the logs or metrics of Turms servers.
-
-
Extreme performance We always try to archive extreme performance in the implementation of all business workflows. Please refer to the source code for details.
- Network
- I/O: The Turms server is a reactive application. All network I/O operations (e.g. database call, Redis call, service discovery call, RPC) are based on Netty to achieve non-blocking I/O. Therefore, the Turms server can make full use of system resources (while traditional servers can't)
- Encoding: Protobuf is used to encode the traffic data between Turms servers and turms clients; Custom encoding without any redundant data is used to encode the RPC requests and responses between Turms servers to ensure extreme efficiency
- Thread
- The Turms server has an excellent thread model, and its peak thread number is constant, which is independent of the number of online users and the number of requests. Since the default number of threads in the access layer of the Turms server is the same as that of the CPU processors, the Turms server can make full use of the CPU cache, and greatly reduce the cost of thread context switching and thread contention compared with traditional servers
- During business logic processing, there are almost no locks, only CAS operations
- Memory
- The Turms server allocates heap or direct memory smartly according to its usage to reduce the memory footprint
- The Turms server refactors parts of MongoDB/Redis client dependencies to ensure that there is no redundant memory allocation in the Turms server, which greatly improves the effective use of memory
- Cache: The Turms server makes full use of the local memory cache
| Name | Summary |
|---|---|
| turms-gateway | A gateway (push server) interacting with clients, and responsible for user authentication, session management, push notification, and load balancing for turms-service servers |
| turms-service | Implements IM business logic, and provides admins with business data management, RBAC, cluster management |
| turms-admin | Provides features such as business data management and cluster management for Turms server cluster |
| turms-client-js | Exposes APIs to interact with the Turms server to implement IM features and underlying driver logic (such as heartbeat). You don't need to know its implementations because it's transparent for developers |
| turns-client-kotlin | ditto |
| turns-client-swift | ditto |
| turms-plugin | When events (such as user going online/offline, message receiving and forwarding, etc) are fired, turms-gateway and turms-service will trigger corresponding custom plugins to facilitate developers to implement custom features |
| turms-plugin-antispam | A plugin based on turms-plugin for the anti-spam protection using Aho-Corasick automaton with double array trie (The time complexity of detection is O(n), and n is the length of target string code points) |
| turms-plugin-minio | A plugin based on turms-plugin for the storage service, and is used to interact with MinIO server |
| turms-data (TODO) | Not yet published. An independent data analysis system based on Flink ecosystem is responsible for business data analysis, and provides underlying data support for the statistics APIs of turms for admins and operational reports of turms-admin |
The architecture design of Turms is derived from commercial instant messaging architectures. The following figure shows the reference architecture of Turms. The services framed by dotted lines are optional services, while the services framed by solid lines are required services. Please refer to Turms Architecture Design for details.
Although there are many open source IM projects in the world, there is only one open source IM project designed for medium and large IM application scenarios: Turms.
| Rocket.Chat | Closed source IM cloud | Turms | |
|---|---|---|---|
| Application scenarios | Team communications | General IM scenarios | General medium to large scale IM scenarios (Making Turms possible for redevelopment) (Note: The first version of Turms does not provide support for living/chat room) |
| Advantages | 1. Provide cloud services by just clicking the mouse to start the cluster and provide services 2. The client implementation is cross-platform and out-of-the-box for users 3. Support a complete and unified UI suite 4. Support rich advanced instant messaging features, such as audio and video conference, file sharing, screen sharing 5. Provide commercial users with technical support |
1. Provide cloud services by just clicking the mouse to start the cluster and provide services 2. The client implementation is cross-platform and out-of-the-box for users 3. Support a complete and unified UI suite 4. Support rich advanced instant messaging features, such as audio and video conference, file sharing, screen sharing 5. Provide commercial users with technical support |
The advantages are the features described above |
| Disadvantages | 1. Only suitable for small-scale applications 2. Narrow application scenarios and hard to customize |
1. It is closed source and cannot be customized. Any project will inevitably have new business requirements after business growth, which needs to be customized. However, IM clouds either do not provide customized services or require high customization fees, and they may misunderstand your requirements, resulting in customized features that cannot meet your business needs well. It will take long-term cooperation to works well with them. But based on Turms, your requirements can be implemented and provided quickly, and the cost is low. Note: For details of the complexity of IM, you can refer to Schema Design 2. Data Privacy. All your user information and message data are stored on IM clouds, which can peep and use your data. Especially for some small IM companies, the data security is not guaranteed at all, and you even need to bear the risk of unrecoverable data loss. 3. The more you use IM clouds, the more you rely on it, the more expensive it is. Most IM clouds provide a certain free quota or trial period, but after the user scale of your product grows, you need to pay a high usage fee or give up the use to start develop your own IM server 4. Technical support is not timely. IM clouds need to provide technical support to a lot of customers at the same time, and the support for your product may lag behind |
1. Only meets the general instant messaging needs, and does not provide some advanced features (for example, no support for audio and video conferencing) 2. The first version of Turms does not support living/chat room 3. Turms server only provides raw data of metrics/logs, and does not provide functions such as analysis and alarms 4. The web-based system administration turms-admin does not provide advanced operation features currently 5. No support for specific business logic and UI 6. Servers are reactive, which is challenging for some developers |
| Comment | It is highly recommended to use Rocket.Chat for team communications | If the IM business scenarios in your product is very common, and there is no custom requirements, and the IM business is not the main business of your product, it is recommended to use IM clouds. But if there is no special requirements, try not to use the IM cloud provided by small companies, otherwise your data security will not be guaranteed |
Although both are open source IM projects, they have completely different application scenarios. Turms is a general instant messaging engine for medium to large scale instant messaging applications. You cannot just hand Turms to your customers (just as most products don't let customers write SQL statements to query business data in the database). However, based on Turms, you can implement all the open-source instant messaging projects on GitHub more efficiently, comprehensively, and extensively |
Considering the positioning of Turms, we do not plan to provide client demo with UI and specific business logic in the near future because:
- It is easy for developers to verify the business features supported by Turms. If you just want to test the business features of Turms, you can run the Turms server without even typing a line of code. Only ten lines of code can realize the login, sending messages, sending friends' requests and other business features, or modify properties to customize various requirements.
- The design and implementation of the demo are closely related to the specific business scenarios, specific programming language, specific technical architecture, and specific OS while Turms has been committed to efficiently meeting various complex and challenging instant messaging scenarios, and we don't want to publish a demo that limits the imagination of developers. And developing and maintaining a demo is also very time-consuming and will slow down the progress of the development of Turms.
The Turms project is licensed under the Apache License 2.0 license, so we don't care whether users plan to make profits from the Turms project. We only require users to comply with the Apache License 2.0 license in your works, such as documents, videos, codes, etc., to mention the information of the Turms project, such as:
Original Project Name：turms-im/turms
Original Project：https://github.com/turms-im/turms
Original Project Documentation：https://turms-im.github.io/docs
-
How is the Turms project profitable?
We do not need to be profitable currently. Of course, we do not exclude profit, but we will not deliberately to write bad documents or to do a bad job in order to earn consulting, training and other expenses. Another thing to mention is that there are indeed many (closed) open source projects that earn service support fees by deliberately writing bad documents and doing a bad job.
-
If profit-making organizations, such as training institutions or companies, cite Turms' documents, or even sell Turms projects as SaaS services, do these profit-making organizations need to pay attention to anything?
We don't care whether your team plans to make a profit from the Turms project. Your team only needs to comply with the
Apache License 2.0license and mention the Turms project information as mentioned above. -
The Turms project is suitable for making SaaS services, so why doesn't the Turms project adopt the AGPL or SSPL license?
We currently do not need to make a profit, and we do not plan to make a profit. We only require users to comply with the
Apache License 2.0license. -
If the Turms project is not profitable, what is the quality of its project?
Our documentation and source code have answered this question for us, and in the open source community, there is no open source IM project that can compete with the Turms project in medium and large IM application scenarios. Another thing to mention is that commercial projects do not mean high quality, and even the quality of documentation and code for many commercial projects is shocking.