This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
- # admin-announcements (1)
- # aleph (1)
- # architecture (1)
- # bangalore-clj (14)
- # beginners (15)
- # boot (89)
- # braveandtrue (1)
- # cider (1)
- # cljs-dev (33)
- # cljsjs (1)
- # cljsrn (147)
- # clojure (149)
- # clojure-quebec (1)
- # clojure-russia (82)
- # clojure-spec (18)
- # clojure-taiwan (2)
- # clojure-uk (15)
- # clojurescript (97)
- # cursive (11)
- # datomic (22)
- # funcool (2)
- # hoplon (53)
- # immutant (16)
- # jobs-rus (8)
- # lambdaisland (1)
- # off-topic (13)
- # om (7)
- # onyx (58)
- # parinfer (6)
- # planck (19)
- # protorepl (2)
- # re-frame (17)
- # reagent (201)
- # rum (6)
- # specter (9)
- # test-check (68)
- # untangled (47)
- # yada (94)
hi @aaelony, have you increased
aeron.socket.so_rcvbuf for aeron previously ?
We are thinking of changing our workflow up a little and I wanted to see if this is a good idea or not. The last stage of our current workflow is a window/trigger. This trigger right now is doing a hell of a lot of stuff and potentially more in the future. The reason is we are collapsing records based on a key and we don’t need to do all of this work on every segment but just this final collapsed segment. My thought was to remove a lot of this from the trigger by sending the collapsed segment back into a kafka topic which would then be backed up by a secondary :in task to finish off the workflow. Does this sound like a good idea ? or is there a better approach?
Right now that's the only way to do sequential aggregations, we have some folks using that approach.
@lucasbradstreet @michaeldrogalis have you guys shared your big announcement yet? 🙂
Not yet, gotta let hype build first (heh, not really, just finishing the blog post)
@gardnervickers: Thnx for the input, just wanted to make sure that sounded reasonable
@asolovyov @robert-stuttaford My "tomorrow" gets later and later every day. Thing about working for yourself is that you get sucked into working really late at night when it's quiet. 🙂
kind of like that silicon valley episode with the datacenter “ Day and Night are all kind of the same thing down here” lol
Haha. Yeah pretty much. I get a reasonable amount of sleep, but I'm busy for sure.
@michaeldrogalis: i totally know what you mean. i've been working from home for over a decade, so i've since cycled back out of that (ultimately) negative pattern. enjoy it while you can manage it 🙂
The big news is out. We just closed a seed round to build a managed platform on top of Onyx.
Now I wish I could show what we've already built. 🙂 That's going to be a few more months though.
that it is. I still want to bring you guys on for some one on one. Waiting for some stuff to finalize and hopefully this can be accomplished
@michaeldrogalis: congrats on the seed round! great to see open source projects with a clear path to monetization
Awesome, thanks! Everything is a balance game now. I've been heads-down on the product for a few months now, hence why I had to slow up on Onyx core a little. Lucas is still 98%+ Onyx dedicated though
I can definitely say that we've built something already that will let you shuttle data between all the existing plugins at way faster engineering speeds with the same flexibility and high performance you have today in Onyx core.
Yep. It's a metered-usage platform. Only pay for what you use. Feels pretty similar to AWS.
Is it going to be compute-only, or is there also going to be a data storage offering ?
It's designed to be holistic if you want it, or piece-meal if you want to interconnect with your existing environment.
So how are you going to handle issues of data locality, where I want my data to be available in, say, Azure data centers ?
Heh, might actually get in trouble for that one. We'll have a beta out pretty soon.
@otfrom: It's like a super-charged environment for using Onyx end-to-end. Everything's just faster to figure out and debug.