[buglungtung]

The funny story behind KanthorQ is that it stemmed from a challenge I faced with another project: an open-source webhook gateway (https://github.com/kanthorlabs/kanthor). After completing that project and starting some benchmarks, I realized I was dealing with issues I had never encountered before.

When something went wrong, I had to scan through a list of events to identify the failed ones. However, doing that with traditional message brokers like NATS.io or RabbitMQ was challenging. I needed an additional layer to store the events and analyze the data. As a result, a simple system required two high-availability components to function properly.

Additionally, backup and restoration were not straightforward with traditional message brokers like NATS.io or RabbitMQ. It's difficult to back up and restore these systems—or at least, I couldn't find a reliable way to do it.

That's why I developed KanthorQ. Now, I have a message broker where data is stored in a database, making it easy to browse, analyze, back up, and restore.