Using Clojure greenfield project is great but what about legacy projects full of toxic decay and code zombies lurking the repo?
Clojure is your post apocalyptic weapon. You don't have to re-write the whole monolith; by switching key parts of the infrastructure we can reduced the number of servers and costs.
Get bragging rights with your managers and higher ups by introducing Clojure and Clojure community practices in large legacy apps. In this installment we’ll explore how to reduce the high IO costs of large scale email processing with Clojure.
Bio: Paco is a developer in Portland Oregon and can be found on twitter at https://twitter.com/kidpollo