This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # adventofcode (31)
- # beginners (97)
- # bigdata (2)
- # boot (276)
- # cider (17)
- # cljsrn (5)
- # clojure (150)
- # clojure-china (3)
- # clojure-conj (8)
- # clojure-greece (1)
- # clojure-india (1)
- # clojure-korea (1)
- # clojure-new-zealand (4)
- # clojure-russia (40)
- # clojure-spec (119)
- # clojure-uk (116)
- # clojurescript (87)
- # code-reviews (110)
- # core-async (4)
- # cursive (11)
- # datomic (26)
- # garden (4)
- # gorilla (7)
- # hoplon (82)
- # humor (1)
- # jobs (2)
- # jobs-discuss (10)
- # luminus (17)
- # onyx (60)
- # planck (2)
- # play-clj (2)
- # protorepl (70)
- # re-frame (121)
- # reagent (7)
- # ring-swagger (3)
- # rum (16)
- # test-check (16)
- # untangled (12)
- # yada (20)
@lucasbradstreet refinement calls are in the cheat sheet, but the guide only mentions the two pre-existing options, so there's no reason to look for it.
What's your position on adding uniqueness-key checks to onyx-local-rt, making it possible to simulate duplicate segments?
@yonatanel Probably not. local-rt isn’t meant to be an exact mirror of core in that regard. The environment itself would need to accrete a good chunk of state to do that check, would be raising the complexity bar a lot.
uniqueness-key will go away in 0.10 by the way. The ABS engine doesn’t need the user to tell it what makes a segment unique since it does barrier injection, which we control.
Heh, we have been saying “a few weeks” for a few months. Things keep coming up. @lucasbradstreet, how’re you feeling?
Maybe this question has been already answered/made, but I was wondering whether there is already someone using Onyx with
node.js peers and/or AWS lambdas
@yonatanel it’s coming along nicely, but I got slowed down a bit because of my move to the US. I’m willing to commit to a technical preview in the next week
@richiardiandrea we don’t know of anyone using Onyx in this way. We have been discussing it a bit, but don’t really have the time to do it ourselves at the moment. The main blockers would be implementing the ZK client so they could coordinate, and the messaging layer which would likely involve some C interop with Aeron
@lucasbradstreet thanks, my question is maybe more whether there is also an abstraction for function calls (I guess at the moment they are resolved only on the JVM?)
onyx-local-rt can do it in clojurescript, though the functions need the metadata on them so they will be exported
However, onyx-local-rt doesn’t feel terribly useful for production use at the moment. If you can do everything you need in one peer it might be OK though
@gardnervickers cool, is it something you are interested in? I think cljs-in-cljs is only necessary for the
resolve part, once the peer "receives" the catalog entry (sorry I am new to the architecture) and it wants to call
ah no Klipse (and replumb, which is what Klipse uses under the hood and of which I am the author 😄) evaulates in the browser
local-rt feels like it could be a good fit to execute as a complex function into Lambda.
actually there is probably a better way...you don't need to resolve the function on Lambda, just trigger it, the problem is how to make it participate in the Onyx framework
but I see that it is doable, first step it is probably to hook it in
Yeah, I was picturing an inversion of control. Lambda is invoking a program that fires up onyx-local-rt. You’re talking about integrating Lambda into Onyx core though, right?
Ah ah, I am fishing 🙂 No but seriously, I see a lot of value in using either one or the other language given this or that constraint (that we have at the new company I am working with)
Any sort of Lambda integration would be useful I’m sure. See how far you can go.
Ok cool I am in the brainstorming phase now but I'll stay in touch if things become concrete
just to give more context, I am also looking at https://aws.amazon.com/step-functions
@richiardiandrea, I started something relevant awhile back, which I've since abandoned: