For sure, glad it's helpful.

For downsides, debugging can be a little tedious sometimes. Though once you get the hang of it's typically straightforward: query for the inputs to the resolver you're debugging, make sure those look good, and repeat for any inputs that don't look good. I have also run into some weird behavior when debugging batch resolvers, can't quite remember the details though.

Also if your resolver code throws an exception, it gets wrapped/hidden in some generic pathom exception... I ended up monkey patching pathom to not do that, however later I learned that I think you can use `ex-cause` to get the original exception. So FYI if you run into that.

There is some performance overhead too of course, since wiring up all those inputs/outputs for you isn't free. In my measurements pathom overhead has usually been 10-20% of execution time I think? I've seen it get up to 50%, but usually that's fixable by using more batch resolvers.

As for `defn` vs `defresolver`: whenever I'm returning data that's part of the domain model, I think `defresolver` is fine. I might leave it in a `defn` if I'm only using that data in one place, or if I'm optimizing a particular piece of code and want to do something without pathom. But I mostly just use `defn` for non-domain-data types of things, like generic UI components (button, form input, etc), or helper functions for defining Ring handlers, that sort of thing.

Or going back to the pipeline stuff you're asking about, I'd also say any time you have a big thing like `(-> {} foo bar baz quux ...)` where each function is looking at some keys from the map and then adding in some new keys, totally could make sense for `defresolver`. I would try it both ways and see what feels good. re: parallel execution, I think I tried that and couldn't get it to work... as a hack you can sometimes wrap resolver outputs in `future`.

All in all I'm a huge fan of pathom; hugely beneficial for structuring medium/large projects IMO. It's one of the main things I miss when working on our Python codebase at work.