If you embed it in your app, then you lose the ability to cycle your app without taking down your broker (which is a bad thing if you use non-persistent messaging as we do). Clearly that trade-off is a win in your situation, but your situation's a bit of an outlier in terms of performance, so the forces that drive you to embed may not be applicable to users with more mainstream performance requirements.
With that being said, I'd be really interested in the ability to expose a RESTful API around the broker so you can get JMX stats faster than JMX will allow, because we've been hampered by how slow JMX is. We're trying to poll dozens/hundreds of destination/consumer/producer MBeans every second to log out status (to help us look for sources of lag within the system), and JMX is completely unable to keep up, so we'd love a better option. I'm not sure if that would be done by embedding ActiveMQ within an app that provides only that RESTful API or by rolling the API into the core broker executable, but if you're still thinking of open-sourcing that code (whether as part of the ActiveMQ project or as a companion project), we'd be interested in using it. Tim On Fri, Apr 17, 2015 at 11:50 AM, Kevin Burton <bur...@spinn3r.com> wrote: > When we initially deployed activemq we took the normal route of using it > with an init.d and run the daemon like we do apache, cassandra, etc. Like > a daemon. > > However, I found that we lean pretty hard on the actual implementation of > ActiveMQ and need to go above and beyond what ActiveMQ provides. > > For example, JMX was too slow for us, so I implemented a basic REST API > that allows us to fetch queue metadata. We went from 15000ms to 20ms to > fetch all the metadata. > > We’re also able to embed other daemons this way such as our own servlets, > metrics, etc. > > Seems like it might be a good idea to encourage ActiveMQ users to embed AMQ > in their own application and look at using BrokerService as more of an API > vs a daemon. > > > > -- > > Founder/CEO Spinn3r.com > Location: *San Francisco, CA* > blog: http://burtonator.wordpress.com > … or check out my Google+ profile > <https://plus.google.com/102718274791889610666/posts> > <http://spinn3r.com> >
