Messaging Brokers are intrinsic part of our infrastructure and our experience with HornetQ has not been really great. We have experienced issues that forced us to perform restarts multiple times a day and sometimes they weren't sufficient to fix the issue and data cleanup was needed resulting in loss of important messages. Lack of documentation, lack of proper support and lack of stability of HornetQ broker are some of the reasons for looking into new Messaging Brokers. During this session I will present the path we have taken to Prioritize Features -> Compare Brokers -> Eliminate -> Benchmark and the findings together with recommendations. This task resulted in implementation of generic messaging broker benchmarking tool in Java, called Benchmark.io which we are intending to open source.