[ANN] Onyx 0.10 final release

We're happy to announce the final release of Onyx 0.10. Onyx is a scalable, distributed, fault tolerant, high performance data processing platform for handling batch and streaming workloads. It's written purely in Clojure, and supports idiomatic Clojure programs on top of it. This version upgrad

[ANN] Onyx 0.9.6: Static Analysis and Elm-grade Error Messages

I'm happy to announce the release of Onyx version 0.9.6. This release of Onyx ships our new static analyzer module, which is in turn bundled with a renderer to deliver significantly better error messages than we were able to show in previous releases. Read about it in our blog post below! Blog

[ANN] Engraver: a tool for managing Onyx clusters

ost: http://www.onyxplatform.org/jekyll/update/2016/03/21/Engraver-A-Tool-for-Managing-Onyx-Clusters.html Cheers, -- Michael Drogalis -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com

Jepsen testing Onyx

Hi everyone, We're happy to share that we've been busy Jepsen testing Onyx over the last few months. We've written a blog post to share the results with how we did it, what we found, and how we fixed problematic areas: Blog post: http://www.onyxplatform.org/jekyll/update/2016/03/15/Onyx-Straps-

[ANN] Doubling down on Onyx

Hi everyone, I'm happy to announce that, starting next week, I'll be supporting the Onyx Platform full time. I want to thank the incredible Clojure community that's helped to make Onyx a successful open source project. Read on in the blog post

[ANN] Onyx 0.8.4: machine-aware optimization

Onyx is a high performance, fault tolerant, distributed data processing platform for Clojure. It uses a data driven API to transparently handle batch and streaming workloads over a variety of storage mediums. I'm happy announce release 0.8.4, which includes our next generation scheduling compon

[ANN] Onyx 0.8.0: Automatic State Management

We're pleased to release Onyx version 0.8.0, which brings with it primitives for automatic state management, failure recovery, windowed computations, and triggers. Onyx is a scalable, distributed, fault tolerant, high performance data processing platform for handling batch and streaming workloa

Re: [ANN] Clojure 1.8.0-RC1 is now available

Upgrading Clojure to 1.8.0-RC1 passed Onyx's full test suite. Thumbs up on our end. On Tuesday, November 10, 2015 at 9:30:47 AM UTC-8, Alex Miller wrote: > > Clojure 1.8.0-RC1 is now available. *This build is a "release candidate"!* > We would appreciate any and all testing you can do on your ow

Onyx Cheat Sheet

Onyx [https://github.com/onyx-platform/onyx] is a distributed, fault tolerant, high performance data processing platform for Clojure that supports batch and streaming workloads. The majority of the surface area of its API is data-driven. We've documented the information model in several ways, an

[ANN] Onyx 0.7.0: 2x Throughput, 5x Latency Improvement

We're happy to announce version 0.7.0 of the Onyx Platform. This release of Onyx features a massive jump in performance with the integration of the new peer-to-peer library Aeron. Additionally, we've begun to open the door for cross language support into Java. Blog post: http://michaeldrogalis

[ANN] Onyx 0.6.0

I'm happy to announce that Onyx 0.6.0 is officially out! Blog post: http://michaeldrogalis.github.io/jekyll/update/2015/06/08/Onyx-0.6.0:-Going-Faster.html GitHub: https://github.com/onyx-platform/onyx Website: www.onyxplatform.org Chat: https://gitter.im/onyx-platform Thanks to all the contrib

[ANN] Onyx 0.5.3: Flow Conditions

Onyx is a distributed, masterless, fault tolerant data processing system for Clojure. Version 0.5.3 is out with a new feature called Flow Conditions. Flow Conditions isolate logic for message routing within your cluster, offering extraordinary flexibility for runtime specification. Blog post:

Re: ANN: Onyx Dashboard 0.5.2.1

Hi Colin, This is well supported within Onyx, and has seen recent progress (http://yuppiechef.github.io/cqrs-server/) The examples should give you a good indication if it's a fit for your problem (https://github.com/MichaelDrogalis/onyx-examples). We hang out in Gitter if you have any question

[ANN] Onyx 0.5.0: The Cluster as a Value

For those unfamiliar, Onyx is a batch/stream processing hybrid distributed platform for Clojure. It uses aggressive data-driven techniques to bridge languages. Onyx 0.5.0 has been released, featuring a new masterless design and a built-in event notification service. Source at GitHub: https://g

Re: Where can one find low hanging fruit for open source contribution?

Hi there, About a week ago, I open sourced Onyx, a new distributed computation platform: https://github.com/MichaelDrogalis/onyx I've been looking for help from developers of all skill levels, though I have 3 or 4 open tasks particularly well suited to someone with intermediate skills. Two ta

[ANN] The long awaited Dire 0.5.0 - Slingshot integration

This feature has been requested for a few months, and it's finally made its way into Dire. I'd like to thank Dylan Paris for sending in a patch to do this. The tl;dr: error handling can now dispatch based on predicates rather than types. Dire: https://github.com/MichaelDrogalis/dire Slingshot:

ANN: Rush Hour - an example Clojure architecture

r.com/post/65274692089/clojure-understood-the-rush-hour-platform -- Michael Drogalis -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are modera

Re: In-order triggering of watches on mutable state

I can precisely exemplify the behavior here: https://gist.github.com/MichaelDrogalis/6123177 On Wednesday, July 31, 2013 11:13:17 AM UTC-4, Michael Drogalis wrote: > > Aaron: Yep, I'm aware - and am using the value provided by the last > parameter. > > This is going to

Re: In-order triggering of watches on mutable state

e > > If you use old-state and new-state rather than the reference, you should > not see your problem. > > --Aaron > > > On Wed, Jul 31, 2013 at 11:00 AM, Michael Drogalis > > > wrote: > >> Problem: >> >> I have a ref representing a queue of

In-order triggering of watches on mutable state

Problem: I have a ref representing a queue of people in line. I add a watch to the ref to print out the contents of the queue whenever it changes. Naturally, and expected, the following can happen if queuing happens in rapid succession: Queue: [] console: "Queue is Mike, John" console: "Queu

Re: [ANN] Dire, Erlang-style error handling

The CL article is really interesting, thanks. What do you think of the idea of using Slingshot's try+ within Dire? On Saturday, December 29, 2012 3:55:13 PM UTC-5, Ben wrote: > > On Sat, Dec 29, 2012 at 12:44 PM, Michael Drogalis > > > wrote: > > I've never seen

Re: [ANN] Dire, Erlang-style error handling

error handler Any way we can make this better? On Saturday, December 29, 2012 1:22:30 PM UTC-5, Ben wrote: > > On Sat, Dec 29, 2012 at 10:13 AM, Michael Drogalis > > > wrote: > > On Saturday, December 29, 2012 9:57:56 AM UTC-5, Adam Clements wrote: > >> One thing

Re: [ANN] Dire, Erlang-style error handling

l like multimethods. I think it's a good idea for users of the supervise function to call their worker/task function and away it goes. If a new handler is defined, the map passed to supervise has to be modified, which violates the Open/Closed principle. That said, if you fork it and give yo

Re: Unseemingly Eager Clojure Apprentice Seeking FizzBuzz Feeback

Use a cond rather than nesting ifs. Otherwise looks good. On Saturday, December 29, 2012 7:35:38 AM UTC-5, Sean Chalmers wrote: > > Greetings all! > > I'm just starting out in the so far wonderful world of Clojure and to help > me get started I had a crack at one of my favourites, the FizzBuzz pr

Re: [ANN] Dire, Erlang-style error handling

012 8:40:28 PM UTC-5, Dave Sann wrote: > > I see joe's thesis is linked on your github page. is this thesis the paper > you are referring to? > Do you have a link to the video you refer to? > > thanks > > Dave > > > On Saturday, 29 December 2012 06:14:34 UT

Re: [ANN] Dire, Erlang-style error handling

: > > Michael Drogalis > writes: > > >Perhaps. Is there anything in the exception object that is useful? I > >passed on it because the implementer of a handler already knows what > >exception occurred. I'm happy to pass it as an argument if we have >

Re: [ANN] Dire, Erlang-style error handling

> Would it make sense for the handler to have access to the exception 'e' ? > > On 29/12/2012, at 6:14 AM, Michael Drogalis > > wrote: > > Hey folks, > > After watching The Language of the System and being directed to Joe > Armstrong's pape

[ANN] Dire, Erlang-style error handling

Hey folks, After watching The Language of the System and being directed to Joe Armstrong's paper on error handling, I concurred that his approach is fantastic. I really wanted the same thing for more rudimentary operations, like file handling. So I wrote Dire https://github.com/MichaelDrogalis/

Re: [ANN] Dibble - A new way to seed databases

ttps://github.com/MichaelDrogalis/zombie > > > > In any case, drop the link here when you find the talk. We should take a > stab at merging these two concepts. > > > > On Sunday, November 11, 2012 6:23:24 PM UTC-5, Brian Marick wrote: > > > > On Nov 11

Re: [ANN] Dibble - A new way to seed databases

uld take a stab at merging these two concepts. On Sunday, November 11, 2012 6:23:24 PM UTC-5, Brian Marick wrote: > > > On Nov 11, 2012, at 2:35 PM, Michael Drogalis wrote: > > Wouldn't it be great to generate rows in a customer table without having > to make up nam

[ANN] Dibble - A new way to seed databases

Hey folks, I recently encountered a situation where developers on a team needed to seed their databases with large amounts of data. The data didn't have to be the same across all machines, it just had to be logical. Thus, the concept of inferential database seeding was born in my little mind!