MQTTnet VS Lazy Cache

MQTT https://github.com/dotnet/MQTTnet

MQTTNet - High perf IOT comms for .NET - https://github.com/dotnet/MQTTnet

I'm trying to use MQTT.Net and so far everything works.. except for event handling.

Like the other guy said it depends on the requirements, but you could implement your own mqtt server with MQTTnet with a few lines of code

For the server we used mosquitto because we already used it in the past (and it's relatively simple), for the client MQTTnet because it's .net and it seemed good enough (mosquitto has a client library too but it's C so I'd have to write some interop). It's a simple protocol so it shouldn't really matter which implementation you use.

We are going to use MQTTNet as the foundation for this article, although the same concepts can be applied with any other MQTT client.

[2] https://github.com/dotnet/MQTTnet

For example, I used MQTTnet which is a very nice (high performance & extensible) library. And it's free/open source. If you're not writing your server code in .NET, then look for whatever broker libraries are available on your server platform.

Leverage Frameworks and Libraries: Numerous libraries and frameworks are available for .NET that can simplify caching implementation and management. Examples include CacheManager, EasyCaching, and LazyCache. Evaluate these options to see if they meet your requirements and can help streamline your caching strategy.

We're using a wrapper library called LazyCache. It works fine.

I wasn't aware of this LazyCache nuget, it would requires a bit of a code rewrite for me to use directly, but it seems nice. The only issue is that I see their AsyncLazy implementation does not do what the stackoverflow post mention.