A Storage-Agnostic Golang Message Queue
A Storage-Agnostic Golang Message Queue
Hello, everyone. Three months ago, I started building my first GoLang package, VarMQ. In this short period, I gained a significant amount of traction from the community, and it resulted in over 140 stars on GitHub. A week ago, to check how it performs, I ran benchmarks with a similar package, Pond, which has been managed for years. Pond is not a message queue, though; however, it can be compared to VarmQ since it shares some similarities, except for its storage system. From the benchmarks, I got surprising results, which are that Varmq is taking 50%+ less memory than Pond and also has good performance metrics in IO tasks. which makes me glad and willing to share with everyone here. Benchmark chart site: https://varmq-benchmarks.netlify.app Overall, I would like to increase the adoption of this package and am willing to hear feedback from you. Regardless, if you like this project, don't forget to hit the Star button. It helps the project grow. Thank you!
Share cardActual performance
Launch Intel predictions
Analyze your own launch →Correct prediction on native model
Similar products
YAMQ – Yet Another (delayed) Message Queue
RudyMQ- A rudimentary message queue
Delayed Message Queue
Use SQLite as a Message Queue
Message queue as a service
A Go service that exposes a FIFO message queue in RAM
Miniqueue – Simple, single-binary message queue in Go
A list of task queue libraries and message brokers
Dead-Simple Message Queue
Mqutils – Universal Go message queue library