This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
@michaeldrogalis: ok, I didn't realize this was here
@noisesmith: What did you mean by "send requests via ZooKeeper?"
I mean, I have an http server that will want work done on its behalf - should it use onyx and have a mutually required lib in order to get the catalog definition, or is there a simpler route to use the messaging system instead?
Kind of application level concern, can't give you bullet proof advice there.
OK. So at least there is a sensible way to make either one work.
I was looking for an answer like "it would be crazy to send a request to an onyx peer group without using the onyx lib" or "it would totally not make sense to have two different jars from different codebases in the same peer group". But if it's flexible enough, I'll just focus on my own design criteria.
So when you use
onyx.api/submit-job, it takes a Clojure data structure and serializes it to ZooKeeper, if thats not clear
Peers fetch the catalog etc from ZK.
So however you want to manage the catalog before
submit-job is your perogative
OK, so maybe all I need is onyx.api, and the catalog, in my client app, and then my onyx peers would define the rest. That seems sensible.
That sounds straightforward.
S'all just Clojure data 😉