Core Clojure Data Structures
Review maps, vectors, lists, and sets as the primary value shapes used to represent records, query results, events, and schema-like contracts.
Use this section as a quick map of the Clojure collections that appear throughout the NoSQL track. Java engineers should focus less on class hierarchies and more on choosing the collection shape that communicates the data contract.
| Structure |
Common NoSQL use |
| Map |
Document, row, item, or event payload. |
| Vector |
Ordered fields, batched results, or pipeline output. |
| Set |
Membership, uniqueness, and tag-like relationships. |
| List |
Code-shaped data and macro-oriented examples. |
In this section
-
Clojure Lists
Understand when Clojure lists matter, how they differ from Java lists, and why code-as-data examples often use list-shaped forms.
-
Clojure Vectors
Use Clojure vectors for ordered values, result batches, and indexed access while keeping immutable collection semantics clear.
-
Clojure Maps
Use Clojure maps as transparent records for NoSQL documents, rows, items, and event payloads that can be transformed with ordinary functions.
-
Clojure Sets
Use Clojure sets for membership, uniqueness, tags, and relationship checks in data-oriented NoSQL code.
Revised on Saturday, May 23, 2026