This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-06
Channels
- # architecture (25)
- # bangalore-clj (1)
- # beginners (21)
- # boot (45)
- # cljs-dev (38)
- # clojure (272)
- # clojure-austin (7)
- # clojure-finland (7)
- # clojure-france (3)
- # clojure-italy (7)
- # clojure-japan (1)
- # clojure-russia (13)
- # clojure-spec (36)
- # clojure-uk (31)
- # clojurescript (96)
- # core-async (15)
- # cursive (16)
- # datascript (3)
- # datomic (97)
- # emacs (107)
- # hoplon (16)
- # jobs (9)
- # keechma (1)
- # luminus (1)
- # off-topic (19)
- # om (39)
- # onyx (15)
- # pedestal (3)
- # planck (22)
- # protorepl (4)
- # re-frame (20)
- # reagent (3)
- # ring-swagger (25)
- # specter (26)
- # test-check (19)
- # testing (1)
- # untangled (381)
all I've found so far is this https://github.com/tvanhens/onyx-kinesis
@otfrom Correct, we don’t have an official one. Should be straight foward to build under 0.10 though.
michaeldrogalis cool. I think the problem atm is finding a good clj kinesis lib (or just wrap the java one)
@otfrom Lemme know if you come up with something good for it 🙂
@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.
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
that's useful to know. I think it is a bit of a trade off. Some libs are better than others. 😄
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. 😕