How to set up MQTTnet server with WebSockets in ASP.NET Core?

Use the separate NuGet package for ASP.NET Core integration, then configure the server with WebSocket options in your middleware. Samples in the repository demonstrate this setup for real-time web applications.

MQTTnet vs M2Mqtt for .NET IoT projects?

MQTTnet is more modern, supports MQTT 5, and has higher performance benchmarks, while M2Mqtt is older but stable. For new developments, MQTTnet is preferred due to active maintenance and broader feature set.

Does MQTTnet work with Azure IoT Hub?

Yes, it's compatible with Microsoft Azure IoT Hub, allowing seamless integration for IoT scenarios using the managed client features for automatic connection handling and message queuing.

How to handle retained messages in MQTTnet server?

You must implement the persistence interface provided by MQTTnet, as it doesn't include built-in storage. This involves coding your own solution, such as using a database or file system for durability.

Is MQTTnet thread-safe for high-concurrency use?

Yes, it's designed for high performance and thread safety, supported by extensive unit tests. However, proper async patterns should be followed to avoid potential deadlocks in multi-threaded environments.

Can I run MQTTnet on Linux with .NET Core?

Absolutely, MQTTnet is compatible with .NET Core and runs on Linux, making it suitable for cross-platform IoT and server deployments without platform restrictions.

What's the real-world performance of MQTTnet beyond benchmarks?

In production, performance depends on factors like network latency and hardware, but the library's optimized design typically sustains high throughput, though custom server logic may impact rates.

MQTTNet — High-Performance .NET MQTT Library

What is MQTTNet?

MQTTnet is a high-performance .NET library that implements the MQTT protocol for communication between devices and applications. It provides both MQTT client and server (broker) components, supporting protocol versions up to 5, and solves the need for reliable, efficient messaging in IoT and other distributed systems.

Target Audience

.NET developers building IoT applications, messaging systems, or real-time communication solutions that require MQTT protocol support.

Value Proposition

Developers choose MQTTnet for its high performance (processing ~150,000 messages/second), lightweight design with no external dependencies, and comprehensive support for MQTT features including TLS, WebSockets, and Azure IoT Hub compatibility.

MQTTnet is a high performance .NET library for MQTT based communication. It provides a MQTT client and a MQTT server (broker). The implementation is based on the documentation from http://mqtt.org/.

Use Cases

Best For

Building IoT applications with .NET that require MQTT communication
Creating custom MQTT brokers for internal or specialized messaging systems
Implementing high-throughput messaging between .NET services
Developing applications that need compatibility with Azure IoT Hub
Adding MQTT client support to .NET desktop or server applications
Prototyping or deploying lightweight MQTT solutions without external dependencies

Not Ideal For

Projects requiring a broker with a built-in graphical user interface for monitoring and management
Teams needing out-of-the-box persistent storage for retained messages without custom implementation
Applications targeting non-.NET platforms where a cross-language MQTT library is essential
Scenarios demanding extensive server-side security features beyond TLS without additional coding

Pros & Cons

Pros

High Performance Benchmarks

Processes approximately 150,000 messages per second in optimized scenarios, as verified in local tests with the TCP channel.

Full MQTT 5 Support

Implements MQTT protocol up to version 5 with a uniform API, ensuring compatibility across different client versions without fragmentation.

Managed Client Automation

The ManagedMqttClient automatically handles connections, subscriptions, and message queuing for higher QoS levels, reducing boilerplate code.

Lightweight and Dependency-Free

Has no external dependencies and minimal overhead, making it easy to integrate into .NET projects without bloating the codebase.

Extensible Architecture

Offers extensible communication channels and interfaces for custom credential validation and message interception, allowing tailored security and logic.

Cons

No Built-in Management UI

The server component lacks an administrative interface or dashboard, requiring developers to build custom tools for monitoring connected clients and messages.

Persistence Requires Custom Code

Retained message persistence must be implemented via provided interfaces, as stated in the README, adding development overhead for data durability needs.

UWP Server TLS Limitation

TLS support is not available for UWP servers, restricting secure communication in Universal Windows Platform applications without workarounds.

Complex Advanced Setup

Features like custom message interceptors and subscription validation require deeper MQTT protocol knowledge, which can steepen the learning curve for novices.

Frequently Asked Questions

What is MQTTNet?

Target Audience

.NET developers building IoT applications, messaging systems, or real-time communication solutions that require MQTT protocol support.

Value Proposition

Use Cases

Best For

Building IoT applications with .NET that require MQTT communication
Creating custom MQTT brokers for internal or specialized messaging systems
Implementing high-throughput messaging between .NET services
Developing applications that need compatibility with Azure IoT Hub
Adding MQTT client support to .NET desktop or server applications
Prototyping or deploying lightweight MQTT solutions without external dependencies

Not Ideal For

Projects requiring a broker with a built-in graphical user interface for monitoring and management
Teams needing out-of-the-box persistent storage for retained messages without custom implementation
Applications targeting non-.NET platforms where a cross-language MQTT library is essential
Scenarios demanding extensive server-side security features beyond TLS without additional coding

Pros & Cons

Pros

High Performance Benchmarks

Processes approximately 150,000 messages per second in optimized scenarios, as verified in local tests with the TCP channel.

Full MQTT 5 Support

Implements MQTT protocol up to version 5 with a uniform API, ensuring compatibility across different client versions without fragmentation.

Managed Client Automation

The ManagedMqttClient automatically handles connections, subscriptions, and message queuing for higher QoS levels, reducing boilerplate code.

Lightweight and Dependency-Free

Has no external dependencies and minimal overhead, making it easy to integrate into .NET projects without bloating the codebase.

Extensible Architecture

Offers extensible communication channels and interfaces for custom credential validation and message interception, allowing tailored security and logic.

Cons

No Built-in Management UI

The server component lacks an administrative interface or dashboard, requiring developers to build custom tools for monitoring connected clients and messages.

Persistence Requires Custom Code

Retained message persistence must be implemented via provided interfaces, as stated in the README, adding development overhead for data durability needs.

UWP Server TLS Limitation

TLS support is not available for UWP servers, restricting secure communication in Universal Windows Platform applications without workarounds.

Complex Advanced Setup

Features like custom message interceptors and subscription validation require deeper MQTT protocol knowledge, which can steepen the learning curve for novices.

Frequently Asked Questions

MQTTNet

What is MQTTNet?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?

MQTTNet

What is MQTTNet?

Overview

Use Cases

Best For

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions

Related Projects

Found a gem we're missing?