@mv We have two Clojure engineers and two JS engineers, plus a UI/UX engineer.

does anyone know some good resources about designing and managing asynchronous system, especially about backpressure and monitoring?

@chrisblom I’m also interested, I looked for Clojure in relation to reactive libraries and saw quite a few, also with some work you could use core.async for the purpose of backpressure.

cool, i've used core.async in the past, but i find it a bit magical and hard to monitor

i look at which libraries to use etc later, i'd like to form a high level overview first.

@chrisblom I would look at this: https://www.youtube.com/watch?v=1bNOO3xxMc0 then read the books recommended by Zach Tellman

It also depends what’s the use case, but for example it would be nice to have a reactive kafka library for clojure, where for example you could determine maximum the amount of messages ‘in flight’. Such that when that limit is reached it stops consuming.

I don’t know what’s possible in #onyx in relation to this

previous versions onyx stopped consuming when a max no. messages are in flight

Nice, maybe I look to #onyx again, it was a bit to complicated to quickly set up.

Hm, I remember that a lot of servers in clojure land dont handle backpressure well. IIRC there was a server designed for exactly this purpose, but I just cannot recall the name.

@chrisblom I found this fairly recent post from the Wallaroo Labs folks to be a nice overview of handling overload, specifically: https://blog.wallaroolabs.com/2018/03/some-common-mitigation-techniques-for-overload-in-queueing-networks/

not Clojure-related, but general principles

good links at the bottom too (including one to that Zach Tellman talk)

anyone else watching Zuck's testimony?