Book Image

Clojure for Java Developers

Book Image

Clojure for Java Developers

Overview of this book

We have reached a point where machines are not getting much faster, software projects need to be delivered quickly, and high quality in software is more demanding as ever. We need to explore new ways of writing software that helps achieve those goals. Clojure offers a new possibility of writing high quality, multi-core software faster than ever, without having to leave your current platform. Clojure for Java developers aims at unleashing the true potential of the Clojure language to use it in your projects. The book begins with the installation and setup of the Clojure environment before moving on to explore the language in-depth. Get acquainted with its various features such as functional programming, concurrency, etc. with the help of example projects. Additionally, you will also, learn how the tooling works, and how it interacts with the Java environment. By the end of this book, you will have a firm grip on Clojure and its features, and use them effectively to write more robust programs.
Table of Contents (14 chapters)
Clojure for Java Developers
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface
Index

Futures


If you have been using Java for a while, you might know the java.util.concurrent.Future class, this is Clojure's implementation of futures and it is extremely similar to Java, only a bit simpler. Its interface and usage are almost identical to promises with a very important difference, when using futures everything will run in a different thread automatically.

Let's see a simple example using futures, in any REPL do the following:

(def f (future (Thread/sleep 20000) "Hello world"))
(println @f)

Your REPL should freeze for 20 seconds and then print Hello world.

Tip

Futures are also cached, so you only need to pay once for the cost of calculation and then you can use them any number of times you want.

At first glance, futures look much easier than promises. You don't need to worry about creating threads or fibers, but there are downsides to this approach:

  • You have less flexibility; you can only run futures in a predefined thread pool.

  • You should be careful if your futures take too much time...