Track practical NoSQL trends for Clojure engineers, including multi-model databases, SQL convergence, machine learning data, GraphQL, and big-data pipelines.
Trends only matter when they change design decisions. This chapter helps Java and Clojure engineers evaluate multi-model databases, AI and machine-learning workloads, GraphQL boundaries, and data-processing ecosystems without chasing novelty.
| Reader focus | Why it matters |
|---|---|
| Multi-model pressure | Know when one database can serve multiple shapes and when that creates coupling. |
| AI and analytics | Prepare NoSQL data for downstream processing without corrupting application models. |
| API layers | Use GraphQL or similar layers where they clarify boundaries, not as a substitute for modeling. |
Read the child lessons as a sequence of design decisions. The goal is not to memorize every database feature, but to learn where Clojure’s data-first style makes database code easier to test, inspect, and operate.