(next clj-muc) feat Alex P (clojurewerkz.org)

Building Your Complete Infrastructure Nerd Way: Lisps.

When faced a problem, Ruby engineers decide to solve it with Ruby. Now
they have a green process problem.
Java engineers decide to stick to Java, and end up having
ProblemFactory. Jokes aside, with Clojure on board
problems get solved often faster and solutions are easier to perceive
and maintain.

Working in as a consultancy agency, it's always hard to push the
technology choices. We decided to go the
OpenSource way, and bootstrapped a prototype with several Clojure
libraries, open-sourced them. Many libs
we built are thin idiomatic wrappers around Java drivers for major
databases or libs.

Topics covered:

• building the polyglot platform with two-side communication, AMQP
• Clojure/Java interoperability, and some our experiences of
  building idiomatic Clojure wrappers
• wrapping your head around core Clojure concepts
• a couple of advices on getting involved and starting writing your
  own clojure code

I'm not going to play an expert here: I'm working with clojure for
less than a year, and still have to learn
a lot, and find something new in that beautiful language every day. I
may not be answer every single low-level
question of yours right away, but if you give me some time to think,
I'll come up with a solution ;)