[Hawkular-dev] kettle build

John Mazzitelli mazz at redhat.com
Wed Feb 25 09:20:12 EST 2015


> > I don't think we want something called like "ExampleDS" in our
> > production builds (which is likely what kettle will eventually
> > become). We provide all hawkular integration components with a
> > datasource that they are free to use - it is called HawkularDS.
> > That's what hawkular devs will use.
> 
> Ok, so, we don't expect people to deploy their own stuff on our
> production builds, right? In the end, it's not a big deal, but I was
> left wondering if there's a reason to deviate from Wildfly here.

I think that is right. I don't think people will be deploying their own stuff into our "kettle". But even if they do (say, they wrote their own hawkular component, whatever that might be), they will have to expect to "play nice" with our integration server or "the nest" and that would mean if they want to use our datasource, they would use our HawkularDS, just as if they want to hook into our bus they would use our connection factory HawkularBusConnectionFactory. Its just part of the infrastructure the Hawkular nest/kettle provides its hosted components.

I know we don't want to ship a product with something called "ExampleDS" - that just seems "wrong" :) Its not a demo or "example" datasource - it is the hawkular datasource! :)

Now, with all that said,

1) When all is said and done, I don't even know if Hawkular will even HAVE a JDBC datasource in the end! We still haven't decided. But for now, we are giving people an embedded H2 database to use. If we switch and go to, say, Postgres, it will still be HawkularDS but just pointing to something different. Or it could completely go away. Who knows? :)

2) I don't even know if this kettle itself is going to be a final product! This was just for the MVP - a prototype to put all our stuff together and see it run. It may be the kettle is just for development purposes. Again, who knows?

In other words, we still don't know how this is going to all end up :) Once more formalized design plans are fleshed out, we'll figure things out.

But let's just roll with it and see how it ends up. As Heiko says, "Just write something" :)


More information about the hawkular-dev mailing list