-
Notifications
You must be signed in to change notification settings - Fork 568
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
48 additions
and
82 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,82 +1,48 @@ | ||
| # Network programming is very bitter, that was before using t-io | ||
| t-io is a high-performance network programming framework developed based on java. Its explosive performance, long battery life stability, extremely easy-to-use API, and rich and sufficient built-in functions make it popular among engineers as soon as it debuts. , and has been continuously passed on by word of mouth | ||
|
|
||
| # source code repository | ||
| [ ](https://gitee.com/tywo45/t-io) | ||
| [ ](https://github.com/tywo45/t-io) | ||
|
|
||
|
|
||
| # Why develop t-io | ||
| Instead of sitting and studying the thick "xxx Authoritative Guide", it is better to stand up and independently develop and create programming APIs that more people can understand at a glance | ||
|
|
||
| #t-io's past and present | ||
| 1. In 2010, talent-tan took over the communication module of the network management system in a major communication company. The old code used traditional IO, and a client needed at least 3 threads to guard, and frequent memory overflow and downtime. Talent-tan was ordered to rewrite the communication module and solve all the problems that the leaders were concerned about. | ||
| 2. In 2012, the talent-nio framework was developed based on nio | ||
| 3. In 2013, I wrote a transparent transmission module in mycat with talent-nio | ||
| 4. In 2014, realized the IM module of Zebo live broadcast with talent-nio | ||
| 5. In 2015, talent-tan began to pay attention to aio technology, and at the same time further abstracted the thread pool, lock processing, and concurrent data structure in talent-nio, so that these "Wang Xietang Qianyan" flew into the "mass code farmers" | ||
| 6. In 2016, talent-nio was rewritten based on aio technology, named talent-aio, and the code was settled in the code cloud, which is low-key and open source | ||
| 7. In 2017, talent-aio changed its name to t-io, and began to spread t-io in the form of news in open source China. In the same year, t-io became a GVP project, and t-io gained a large number of users | ||
| 8. In 2018, peripheral products such as tio-http-server, tio-websocket-server, and tio-webpack were implemented based on t-io. These products not only verified the excellence of t-io, but also promoted the progress of t-io | ||
| 9. In 2019, a Huawei team conducted a 3-6 month-long copying extreme pressure test on a smart product based on t-io. t-io withstood the test and made a solid foundation for officially entering Huawei's open source optimization library. foreshadowing | ||
| 10. In 2020, t-io will officially enter Huawei's open source optimization library. The first commercial IM Tanchat based on t-io will be officially launched. The cluster version of t-io will also be officially developed and passed the pressure test. | ||
| 11. In 2021, customer feedback based on t-io's research and development of Tanchao is very stable | ||
| 12. In 2022, Tanchat, a cluster version based on t-io’s research and development, won the ultimate reputation from users, and at the same time brought a long-term financial guarantee for t-io’s continuous investment | ||
|
|
||
| # t-io ecology | ||
|
|
||
| | Component/Framework/Product | Description | Remarks | | ||
| | ----- | ----- | ----- | | ||
| | tio-http | http server based on t-io | http server of all official products of t-io adopts tio-http | | ||
| | tio-websocket | websocket server based on t-io | all official websocket servers of t-io use tio-websocket | | ||
| | TioMQ | mqtt broker based on t-io | Server: broker.tiomq.com; Port: ws: 8083, wss: 8084, mqtt: 1883, mqtts: 8883; [mqtt-client test tool] (https://www.tiocloud.com/tiomq-website/product/client.html) | | ||
| | TioMeter | mqtt stress testing tool based on t-io | If you need mqtt stress testing, [contact t-io official website business customer service] (https://www.tiocloud.com) | | ||
| | TioMQ Enterprise | Large-scale Internet of Things access platform based on t-io | If you have any cooperation needs, [contact t-io official website business customer service] (https://www.tiocloud.com) | | ||
| | tio-smpp | smpp protocol based on t-io | If you need cooperation, [contact t-io official website business customer service] (https://www.tiocloud.com) | | ||
|
|
||
| # Pain points solved by t-io | ||
| The starting point of t-io is to solve the pain points of users in network programming. Its mission is to make the world no longer have difficult network programs to develop. Let's see the surprises t-io brings to users | ||
| 1. Easy to learn and easy to use. The reason why talent-tan created t-io is because similar products on the market cost a lot to learn, so when designing the API, we pay special attention to user acceptance. The first batch of t-io users mastered t-io just by watching the demonstration project provided by t-io | ||
| 2. Roll over the data monitoring capabilities of all well-known similar products - not only provide comprehensive monitoring data, but also ensure excellent performance | ||
| 3. Built-in heartbeat timeout check, heartbeat timing sending capability | ||
| 4. The extremely polished underlying cluster capability can seamlessly solve the cluster requirements of large-scale products such as IM and Internet of Things | ||
| 5. Automatically reconnect when disconnected | ||
| 6. t-io measured performance 1: 1.9G memory stably supports 300,000 TCP long connections: https://www.tiocloud.com/61 | ||
| 7. t-io measured performance 2: use t-io to run 10.51 million chat messages per second: https://www.tiocloud.com/41 | ||
| 8. t-io measured performance 3: Netty and t-io comparison test results: https://www.tiocloud.com/154 | ||
| 9. Built-in ack message capability | ||
| 10. Built-in half-pack sticky bag processing | ||
| 11. Self-created tool libraries such as synchronous locks, synchronous safe thread pools, and synchronous data structures, providing rich out-of-the-box APIs for business applications | ||
| 12. Built-in slow attack defense mechanism to help applications automatically blacklist suspected IPs | ||
| 13. Rich ecology, currently http, websocket, mqtt and a large number of private protocols have been implemented with t-io | ||
| 14. Low requirements for development engineers, saving labor costs for enterprises | ||
| 15. Excellent performance, saving hardware deployment costs for enterprises | ||
|
|
||
| # t-io documentation | ||
| https://www.tiocloud.com/doc/tio/85 | ||
|
|
||
| # t-io technical white paper | ||
| ["t-io Technical White Paper"](https://www.tiocloud.com/tio.pdf) | ||
|
|
||
| [](https://www.tiocloud .com/tio.pdf) | ||
|
|
||
|
|
||
| #t-io word of mouth | ||
|
|
||
|  | ||
|
|
||
|  | ||
|
|
||
|  | ||
|
|
||
|  | ||
|
|
||
|  | ||
|
|
||
|  | ||
|
|
||
| # t-io use cases | ||
| [](https://www.tiocloud .com/2/case/index.html) | ||
|
|
||
| #t-io witnesses history | ||
|  | ||
| ## Introduction to t-io | ||
| T-io is a network programming framework developed based on Java AIO | ||
| ## Design Mission | ||
| Reduce the difficulty and complexity of network programming, allowing business developers to focus only on business design and implementation, without spending too much time on network programming details, multi-threaded security, and concurrency performance | ||
| ## Function Introduction | ||
| 1. **Automatic heartbeat processing**: heartbeat timeout detection (server side), heartbeat timing sending (client side) | ||
| 1. **User Management**: TiO2. bindUser(), TiO2. getByUserid() | ||
| 1. **Token Management**: TiO2. bindToken(), TiO2. getByToken() | ||
| 1. **Group Management**: TiO2. bindGroup(), TiO2. getByGroup() | ||
| 1. **Synchronous sending**: TiO2. synSend(), requires protocol cooperation | ||
| 1. **Block sending**: TiO2. bSend(), wait for the message to be successfully sent before returning | ||
| 1. **Asynchronous sending**: tio. send(), putting the message into the queue for sending | ||
| 1. **Unified TCP&UDP Programming API**: Except for slightly different startup codes, the business oriented APIs are almost identical. Provides great convenience for one click switching between TCP/UDP | ||
| 1. **Protocol Adaptation**: Different protocols can be converted into the same protocol through protocol conversion, facilitating unified business processing | ||
| 1. **Single channel traffic monitoring**: time of last received business message packet, time of last sent business message packet, time of last received byte, time of last sent byte, time of last packet entering the sending queue, time of ChannelContext object creation, time of first successful connection, time of connection closure, number of bytes sent by this connection, number of packets sent by this connection, number of bytes processed by this connection, number of packets processed by this connection, time taken to process message packets, number of bytes received by this connection, number of TCP/UDP packets received by this connection, number of packets received by this connection T count, heartbeat timeout count, average number of bytes received per TCP, average packet processing time, average number of business packets received per TCP | ||
| 1. **Channel Group Traffic Monitoring**: Refer to GroupStat.java | ||
| 1. **Resource Sharing**: When the same JVM starts multiple servers, the resources of each server can be directly shared, simplifying programming and statistics | ||
| 1. **Automatic reconnection**: When the client disconnects, t-io provides an automatic reconnection mechanism | ||
| 1. **Cluster (attached to commercial products)**: T-IO has a powerful clustering capability built-in, supporting single machine clusters, dual machine clusters, and multi machine clusters. Business nodes can switch freely between servers in each cluster | ||
| 1. **Subscription Tree (attached to specified commercial products)**: t-io has a powerful high-performance subscription tree built-in, which can easily complete subscription, publishing and other capabilities | ||
| 1. **MQTT protocol (attached to specified commercial products)**: t-io has built-in mqtt protocol, including server-side and client-side | ||
| ## Ecological and Case Introduction | ||
| ### HTTP server | ||
| Tio HTTP has implemented the HTTP protocol and built-in an MVC, which can replace containers such as Tomcat and Jetty to complete HTTP access | ||
|
|
||
| ### Websocket server | ||
| Tio websocket has implemented the websocket protocol, and currently many users use it as their websocket access server | ||
|
|
||
| ### MQTT stress testing tool (commercial product) | ||
| TiOMQ Meter is an MQTT stress testing tool developed based on t-io and swing. It can not only test pure MQTT protocol servers, but also test adaptive MQTT protocols | ||
|  | ||
|
|
||
| ### Network debugging tool (not open source) | ||
| Tio Network Debug is a network protocol debugging tool developed based on t-io and swing, mainly used for early protocol integration of products | ||
|  | ||
|
|
||
| ### MQTT client (free) | ||
| Please refer to:[https://www.tiomq.com/product/client](https://www.tiomq.com/product/client) | ||
|  | ||
|
|
||
| ### TiOMQ Platform (Commercial Product) | ||
| This is an IoT platform, details can refer to:[https://env1.tiomq.com](https://env1.tiomq.com) | ||
|  | ||
| ### Other cases | ||
| More ecological or case studies can be found at [https://www.tiocloud.com/1/case/](https://www.tiocloud.com/1/case/) View | ||
|
|
||
| ## Business cooperation | ||
|  |