I have been using message brokers for some time now, primarily MQTT, and I like it a lot. It’s light, robust, and trustworthy—what’s not to like?

The Problem

The problem I have is not with MQTT or any Message Broker, but with the concept itself. I just need to send messages and get responses to those. I understand that this breaks the paradigm and takes out all the essence of message-based architecture, but hey, I just need a feature, regardless of paradigms.

The Solution: Mb.APIfyer

Since I couldn’t find any off-the-shelf solution, I decided to make my own. It turns out to be cool, so I am happy to share it with everyone. Its name? Mb.APIfyer, where Mb stands for Message Broker and APIfyer, well, it speaks for itself.

The goal of my little .NET class library is to convert Message Brokers to APIs, or at least make them API-ish.

How It Works

To be more precise, the only thing Mb.APIfyer does is wrap MQTT (and potentially other message brokers in the future) and create a callback when a message has been answered.

Current Status

The project is still in its very early stages and has hardly been tested, but I would love to hear some feedback about it!

Try It Out

Here’s the repo: Github Link. Give it a spin and let me know what you think!

Conclusion

Mb.APIfyer is an attempt to bridge the gap between message brokers and APIs. While it’s still in its infancy, I hope it can be useful to others who face similar challenges. Feedback and contributions are welcome!