Development Environment for Clojure NoSQL Work

Tooling should support fast feedback, not become the lesson. This section orients the development setup needed for Clojure NoSQL work: command-line tools, editor integration, REPL habits, and local database access.

Read the child lessons as setup decisions. The goal is to make the NoSQL examples runnable and inspectable, then return quickly to modeling, queries, and operational trade-offs.

In this section

• Install Clojure and Leiningen
  Set up the Clojure CLI and Leiningen so Java engineers can run REPL sessions, build projects, and execute the NoSQL track examples.
  • Install Clojure on macOS
    Install the Clojure CLI and Leiningen on macOS, verify the tools, and avoid setup pitfalls that slow down REPL-driven NoSQL work.
  • Install Clojure on Windows
    Install Clojure and Leiningen on Windows with a JVM setup that can run REPL sessions, tests, and database-backed examples reliably.
  • Install Clojure on Linux
    Install Clojure and Leiningen on Linux, verify the command-line tools, and prepare a stable shell environment for NoSQL development.
• Configure Clojure Editors
  Choose and configure an editor setup that supports inline evaluation, namespace work, and fast feedback for Clojure database code.
  • Use IntelliJ IDEA and Cursive for Clojure
    Configure IntelliJ IDEA with Cursive so Java engineers can keep familiar project navigation while adopting REPL-centered Clojure workflows.
  • Use Emacs and CIDER for Clojure
    Set up Emacs with CIDER for connected REPL sessions, inline evaluation, debugging, and fast inspection of Clojure data transformations.
  • Use VS Code and Calva for Clojure
    Configure VS Code with Calva for approachable Clojure editing, inline evaluation, and REPL-driven feedback during NoSQL examples.
• Work with the Clojure REPL
  Use the Clojure REPL as a practical feedback loop for evaluating forms, inspecting data, and tightening database integration code.
  • Clojure REPL Basics
    Learn how the Clojure REPL evaluates forms, loads namespaces, and supports quick experiments before code is committed to a project.
  • Practice REPL-Driven Development
    Use REPL-driven development to evolve Clojure functions, inspect intermediate data, and reduce the build-run-debug cycle familiar from Java.
  • Effective REPL Use
    Apply practical REPL habits that keep interactive Clojure development repeatable, observable, and useful for database-backed JVM systems.