[whiteros_e]

Lack of documentation around performance related stuff and high memory usage because of immutable data structure.

Otherwise it's great. I try to do it in my free time since most of the clojure services are stable(in terms of features) and we are just scaling it up as we see increase in traffic but it's not really helping right now.

[seancorfield]

I guess it depends what the tech stack was before?

Where I work, we were previously a ColdFusion shop when I joined, and after a false start with Scala, I introduced Clojure and it stuck: we cross-trained the CF devs and slowly rewrote the platform from the bottom up in Clojure.

We had struggled with automated deployments, and the size of servers, when we were a CF shop but after the switch to Clojure we had a fully-automated deployment pipeline, with rolling cluster updates, and much smaller servers than we needed before, running more processes than before.

[whiteros_e]

The platform was written in Clojure from ground up since the team was small and rest of the company was using Clojure mostly in combination of Java.

Now most of the company moved out of Clojure for various reasons but they didn't try to write performant code and instead just chose to rewrite which I want to avoid. Try as much as possible before deciding to rewrite since rewrite is expensive given the codebase has lot of things.

I am glad, it's not Java though.