It was just last April that
we announced our plans for the second
major release of Immutant, code-named The Deuce. And today, a year
later, we're happy to announce the end of our beta cycle and the first
official release of Immutant 2.0.0.
We'd like to send out a big, fat THANK YOU! to all our early
adopters who provided invaluable feedback on the alpha, beta, and
incremental releases. It was a total community effort.
From this point forward, we're going to stick to the 3-digit release
naming convention, so no more
-betaX suffixes, just
What is Immutant?
In case you didn't know...
Immutant is an integrated suite of Clojure
libraries backed by Undertow for web, HornetQ for messaging,
Infinispan for caching, Quartz for scheduling, and Narayana for
transactions. Applications built with Immutant can optionally be
deployed to a WildFly cluster for enhanced features. Its fundamental
goal is to reduce the inherent
in real world applications.
What's changed in this release?
The only change in this release since beta3 is a fix for a race
condition in scheduling that generally only manifests on slow
How to try it
There is no longer any "installation" step as there was in 1.x. Simply
add the relevant dependency to your project as shown on Clojars. See
the installation guide for more details.
The guides included in the apidoc are the best source of
information, and our Feature Demo application provides working code
samples demonstrating all the Immutant namespaces. Its
includes simple instructions for getting started at a REPL or command
line, packaging and various deployment options, e.g. a standalone
"uberjar", a WildFly cluster, Heroku and OpenShift.
If you're already familiar with Immutant 1.x, you should probably take
a look at our migration guide.
Get In Touch
If you have any questions, issues, or other feedback about Immutant,
you can always find us on #immutant on freenode or
our mailing lists.