Skip to content
This repository has been archived by the owner. It is now read-only.
Go to file

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Die Roboter

Wir laden unsere Batterie.
Jetzt sind wir voller Energie.

Wir sind die Roboter.

Wir funktionieren automatik.
Jetzt wollen wir tanzen mechanik.

Wir sind die Roboter.

Wir sind auf Alles programmiert.
Und was du willst wird ausgeführt.

  • Die Roboter by Kraftwerk

The Robots get your work done in an straightforward way.


(ns die.roboter.example
  (:require [die.roboter :as roboter]))

;; starting up
(roboter/work) ; on the worker nodes (this will block)

;; ordering around
(roboter/send-off `(println "Boing, Boom Tschak.")) ; returns immediately

(let [f (roboter/send-back `(slurp "/etc/hosts"))]
  (println @f)) ; when you need a return value back, returns a promise

Jobs will not ack to the server until they've completed successfully, so workers that throw exceptions or disappear entirely will have their jobs automatically retried.

Exceptions occurring in send-back calls will be propagated back to the caller and returned upon deref. When using send-off by default failed jobs will simply log using, but you can rebind *exception-handler* to respond in your own way, including acking the message back to the server:

(defn handle-tachyon [e msg]
  (if (re-find #"tachyon" (.getMessage e)) ; tachyon failures don't get retried
    (com.mefesto.wabbitmq/ack (-> msg :envelope :delivery-tag))
    (println "Oh, we got trouble!" (.getMessage e))))

(binding [roboter/*exception-handler* handle-tachyon]

By default each job has five minutes to complete before it is considered hung and are killed, returning its work to the queue. The timeout can be overridden by rebinding die.roboter/*timeout* or passing in a :timeout config key to the work function. You can also avoid timing out by calling the die.roboter/report-progress function, which resets the timer back to the start.

AMQP is used as the transport. RabbitMQ is a popular choice. Most functions take an optional config argument that can be used to specify the AMQP connection settings, but you can also use the with-robots macro to bind it dynamically.

(roboter/send-off '(println "Greetings, programs") {:host ""})

(roboter/with-robots {:username "flynn" :password "reindeerflotilla"}
  (roboter/send-off `(println "Started working on" ~hostname))


Image and lyrics quoted above copyright © 1979 Kraftwerk.

Code copyright © 2011 Phil Hagelberg.

Distributed under the Eclipse Public License, the same as Clojure.


The Robots get your work done in an straightforward way.



No releases published


No packages published