Clojurians Log v2

I am so protocolled out these days that I would rather reach for the 10+ years old ones that are still around today.

I wish I could forget about NATS 😄

Reminds me of the quote by Andrew S. Tanenbaum: "The nice thing about standards is that you have so many to choose from."

@ben.sless why would you want to forget about NATS. Asking for a friend.

Mostly because I'm not enjoying it, and it seems like you will want something else - either a mq like Rabbit or Artemis, or a durable partitioned log like Kafka. What problem does nats solve that isn't covered by these two categories?

So I’m not an infra person, just a dev, and for me, the most important things are that I can stick stuff in one end and get it back out in the other through a reasonable Clojure interface. As for our infra people, they threaten to quit whenever someone mentions Kafka, but were quite happy with nats.

Do you care about the order in which things come in and out? are there broadcast semantics? Do you need persistence? Is HTTP enough?

Or ZeroMQ

As long as the ordering is mostly right, it’s good enough. We do use persistence, but only for a limited period of time, and for our purpose, HTTP seems to be enough. For certain parts of our use cases we’re replacing Redis pub/sub, so a step up for us anyhoop. And, again, as an app dev and not an infra person, I care more about the interfaces than I care about the impl and running of the queue. Whether it runs on UDP, TCP, HTTP or whatever, is not really a concern of mine as long as the data arrives in a timely fashion.

Are you based in Canada or something?

Yep! I’m in Ottawa.

In Belgium you see it as well. Luxembourg in two different spellings.

Only a very few people. But yeah, it’s frustrating

Yes very true, its only a few!

The good news: No fiddling with a broken tire and those patches and then inevitably having a flat tire again giving up and buying a new one. I was already prepared for much worse!