Fork me on GitHub
#onyx
<
2017-03-06
>
otfrom14:03:50

Does anyone know of any onyx stuff to connect to kinesis?

Travis14:03:09

I don’t think there are any official plugins built for it

otfrom14:03:21

camechis thx. At least I'm not missing anything. 😄

michaeldrogalis15:03:35

@otfrom Correct, we don’t have an official one. Should be straight foward to build under 0.10 though.

otfrom16:03:00

michaeldrogalis cool. I think the problem atm is finding a good clj kinesis lib (or just wrap the java one)

michaeldrogalis16:03:08

@otfrom Lemme know if you come up with something good for it 🙂

otfrom16:03:40

michaeldrogalis it depends on a few things, but if we do then we'll open source it

lucasbradstreet17:03:42

@otfrom I’m happy to help with questions about a kinesis plugin. I’ve been meaning to build one for a while, but we really don’t have the time to do it ourselves right now.

otfrom17:03:33

lucasbradstreet cool. thx. I'll send various mastodonians here when they need help. 😄

otfrom17:03:45

did you have an idea of which lib you'd base it on?

lucasbradstreet17:03:22

Personally we’ve tended more and more towards using straight java libs without any clojure wrappers. In this case, that would be com.amazonaws/amazon-kinesis-client. It makes it easier to not worry about performance and breaking peoples dependencies. That said, use whatever library you want to. The hard part is getting it up and running and tested and we can switch over to the unwrapped library later

otfrom18:03:35

that's useful to know. I think it is a bit of a trade off. Some libs are better than others. 😄

michaeldrogalis18:03:11

The devil is whether or not the library’s going to be maintained. Even if the API is better, you can still get sunk if it’s just going to rot. 😕

otfrom20:03:50

that is indeed an issue