We are very happy to announce the release of the new version. This update brings a lot of new features. The most noteworthy thing is that we gradually start to support distributed, which means that you can process data through multiple servers instead of the original For single-machine processing, we also store the telemetry data separately. While the original single-table method is also supported, a sub-table and time series database are added. The main functions of the update are as follows:
-
EFCore.Sharding supports sub-table storage. The default is monthly storage. According to the amount of data, you can modify it to daily or on time.
-
Through Maikebing.Data.Taos we support Taosi Data's time series database TDengine, Maikebing.Data.Taos is currently the only and most complete TDengine support component in the .Net ecosystem.
-
Built-in ZeroMQ service to support distributed message processing based on ZeroMQ.
-
The EventBus message bus is realized through CAP, and ZeroMQ message bus support is supported through CAP.Extensions, which can achieve pure .Net ecology.
-
The message data can be stored in MongoDB LiteDB PostgreSql through CAP.
-
Through CAP, messages can be produced and consumed by RabbitMQ Kafka ZeroMQ. When there are multiple servers, one can be used as the main server, and the other can be used as auxiliary servers to process all collected data.
When this new version was released, we had already used it in the production environment. This month's data has reached more than 30 million, 2,000 devices, and more than 50,000 test items.
In addition, we are also participating in the 2020 OSC China Open Source Project Selection , please search iotsharp and cast your valuable vote.
https://www.oschina.net/project/top_cn_2020?utm_source=projectdetail
Or directly visit the link below to vote.