[Hawkular-dev] agent implementation

Time to start thinking about the agent. As you probably know, the "nest" started out being the "agent" - but it worked out to be something we could use for the server components and it ended up being used for the "kettle" - hosting everything (console, server components, data storage, etc). We can still use the "nest" for agents - that's not a problem. My question is - what do people think about that? So, what do you think the Hawkular agent should "be"? I see three options - Feel free to suggest others: (I mention only one PRO/CON for each, though I'm sure there are many more) 1) It could be our own homegrown Java app (similar to what RHQ did, which means we build out our own agent container). * PRO: We put in and control everything that goes into it - however big it gets (code size and runtime footprint size) is based on what we explicitly put in it. * CON: We put in and control everything that goes into it :) It is not trivial to implement classloading isolation and plugin mechanisms. 2) Or it could be built on top of WildFly (either use the "nest" or use WildFly Core) * PRO: We don't worry about things that WildFly gives us for free (e.g. JBoss Modules for plugin/deployments and classloading isolation; if we want, we can get EE capabilities) * CON: The runtime footprint might be larger than we want or what customers expect. 3) Or it could be built on top of something else (Vert.x? Something else)? * PRO: Depending on the technology, might provide us with a smaller runtime footprint than a full WildFly container * CON: Depending on the technology, might not provide us all the capabilities we want What are your ideas for what you think the "agent" should look like? --John Mazz