TurboMqtt banner
petabridge petabridge

TurboMqtt

Development community

Description

The fastest Message Queue Telemetry Transport (MQTT) client for .NET.

Installation

This entry records only its repository, not the path inside it, so there is no exact command to give. Open the source below and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

README

TurboMqtt

[TurboMqtt](https://github.com/petabridge/TurboMqtt) is a high-speed Message Queue Telemetry Transport (MQTT) client designed to support large-scale IOT workloads, handling over 100k msg/s from any MQTT 3.1.1 or MQTT 5.0 broker.

![TurboMqtt logo](https://raw.githubusercontent.com/petabridge/TurboMqtt/dev/docs/logo.png)

TurboMqtt is written on top of [Akka.NET](https://getakka.net/) and Akka.Streams, which is the secret to its efficient use of resources and high throughput.

Key Features

  • MQTT 3.1.1 and MQTT 5.0 support — Full support for both protocol versions, validated against EMQX 5.x;
  • Extremely high performance - hundreds of thousands of messages per second;
  • Extremely resource-efficient - pools memory and leverages asynchronous I/O best practices;
  • Extremely robust fault tolerance - this is one of Akka.NET's great strengths and we've leveraged it in TurboMqtt;
  • Supports all MQTT quality of service levels, with automatic publishing retries for QoS 1 and 2;
  • Full OpenTelemetry support;
  • Automatic retry-reconnect in broker disconnect scenarios;
  • Full support for IAsyncEnumerable and backpressure on the receiver side;
  • Automatically de-duplicates packets on the receiver side;
  • Automatically acks QoS 1 and QoS 2 packets;
  • TLS/SSL support with mutual TLS and custom certificate validation.

Simple interface that works at very high rates of speed with minimal resource utilization.

Documentation

Document Description
QuickStart Install, connect, publish, and subscribe in minutes
Connection Lifecycle Client states, reconnection behavior, DisconnectAsync vs DisposeAsync
Quality of Service (QoS) When to use QoS 0, 1, or 2; backpressure and