Crux Earth Assignment: Getting Started

A Tale of Time and Space

Crux Earth Assignment: Getting Started

July 22, 2019
Johanna Antonelli

earth pluto mercury neptune saturn jupiter comet planet a


Welcome to the official Crux tutorial, which complements the official documentation.

If you’re new to Crux and want to get a practical hands-on guide, you’re in the right place.

The Story

It’s the year 2115. You have been hired by an inter-planetary bank, Helios Banking Inc. Your task is to travel around the solar system completing assignments using Crux.

You have been given a company spaceship so transport won’t be a problem. Space Customs require all astronauts to complete a flight manifest for every journey. You also have a handy Crux manual with you so you can read up on some background information before you get stuck into each assignment.

Let’s begin.


You need to get Crux running before you can use it.

Choose your path:

You are not familiar with Clojure You are familiar with Clojure

Follow the Nextjournal edition of this tutorial.

Continue to use Crux by adding as a dependency in either your project.clj or in your deps.edn.


In your project

You use Leiningen to set up a new app. Crux can be included as a dependency in your project.clj as:

[juxt/crux-core "RELEASE"]

You start the REPL with the command lein repl and require Crux:

(require '[crux.api :as crux])

You are now ready for your first assignment, so you head over to the Space Port.

In your deps.edn

Update your deps.edn with Crux as a dependency and create a namespace for Crux.

  juxt/crux-core {:mvn/version "RELEASE"}
  (:require [crux.api :as crux]))

Space Port

On entering your spaceship, you notice a flashing blue light on the left of your communications panel. You submit an iris scan to unlock your first message.

A warm welcome from the Helios family.

For your first assignment we would like you to go to Pluto and help Tombaugh Resources Ltd. set up their stock reporting system. There will be a ticket with more information waiting for you upon your arrival. Find Reginald if you have any questions.

Safe journeys, and don’t forget to fill in your flight manifest. They won’t let you land without one.

— Helios Banking Inc.

Power up

Before you leave you must fill in your flight manifest. To do this, you must first set up a Crux node. You want to get started as quickly as possible so you decide to use Crux’s inbuilt standalone node.

You read the Crux manual entry for the standalone node to make sure this is OK.

If you want to get up and running with Crux fast, consider using the standalone node. There is a Crux inbuilt standalone node which is the most simple way to start playing with Crux. Bear in mind that this does not store any information beyond your session.

For persistent storage consider using RocksDB and for scale you should consider using Kafka.

(def node (crux/start-node {}))
— Crux manual
Read More

You decide this is OK, and so define your with the standalone Crux node.

Flight Manifest

You take a look around your ship and check the critical levels.

You read the manual entry for putting data into Crux.

Crux takes data in document form. Each document must be in Extensible Data Notation (edn) and each document must contain a unique :crux.db/id value. However, beyond those two requirements you have the flexibility to add whatever you like to your documents because Crux is schemaless.

— Crux manual
Read More

Just as you’re about to write your manifest, one of the porters passes you a secret note and asks you to deliver it to a martian named Kaarlang. They are certain you will meet Kaarlang on your travels and so you see no harm in delivering the note for them.

(def manifest
  {:crux.db/id :manifest
   :pilot-name "Johanna"
   :id/rocket "SB002-sol"
   :id/employee "22910x2"
   :badges "SETUP"
   :cargo ["stereo" "gold fish" "slippers" "secret note"]})

You put the manifest into Crux.

(crux/submit-tx node [[:crux.tx/put manifest]])
;;=>#:crux.tx{:tx-id 0, :tx-time #inst "2020-06-18T13:54:08.375-00:00"}

This is put, one of Crux’s four transaction operations. Check that this was successful by asking Crux to show the entity history.

(crux/entity-history (crux/db node) :manifest :asc)
;;=> {:crux.tx/tx-time #inst "2020-06-18T13:54:08.375-00:00",
;;    :crux.tx/tx-id 0,
;;    :crux.db/valid-time #inst "2020-06-18T13:54:08.375-00:00",
;;    :crux.db/content-hash #crux/id "0ab888b62775eea2eb2fffe10c9f6bfbf661a792"}

Which returns the history of the provided entity id at this point in time.

You can use :asc or :desc flag with entity-history for the ascending or descending history respectively.

Click on Pluto to take you to your first assignment.