An ADO.NET provider for TDengine supporting native, WebSocket, and RESTful protocols with Schemaless and Stmt features.
IoTSharp.Data.Taos is an ADO.NET provider for the TDengine time-series database, allowing .NET applications to connect and interact with TDengine using native, WebSocket, or RESTful protocols. It solves the problem of efficient data access and manipulation in IoT and time-series applications by providing features like Schemaless bulk inserts and parameterized statements.
.NET developers building IoT platforms, time-series data applications, or systems that require high-performance data ingestion and querying with TDengine.
Developers choose this provider for its multi-protocol flexibility, performance-optimized bulk operations, and seamless integration with the .NET ecosystem, including Entity Framework Core and ASP.NET Core health checks.
ADO.NET, ORM,Stmt,TDengine
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Supports Native, WebSocket, and RESTful protocols, allowing deployment in environments without native dependencies (e.g., WebSocket is pure C#).
Implements Schemaless for TSDB_SML_LINE_PROTOCOL and TSDB_SML_JSON_PROTOCOL, enabling high-performance data ingestion compatible with InfluxDB formats.
Provides Stmt for prepared statements, enhancing security by preventing SQL injection and optimizing query execution.
Compatible with TDengine Cloud services and self-hosted deployments, with configurable connection strings for diverse setups.
Includes ASP.NET Core health checks and ADO.NET provider, though EF Core integration is deprecated.
The IoTSharp.EntityFrameworkCore.Taos package is explicitly noted as deprecated, limiting ORM-based development and future compatibility.
RESTful protocol lacks support for Schemaless bulk inserts and parameterized statements, reducing functionality compared to other protocols.
Using Native protocol requires installing the TDengine client library (libtaos), adding setup complexity and potential cross-platform issues.
README provides basic examples but lacks detailed guides for complex scenarios like large-scale deployments or troubleshooting.