Compare horizontal and vertical scaling options for Clojure NoSQL systems before changing topology or runtime size.
This section bridges the chapter overview and the detailed lessons below. For Java engineers, the practical question is how to handle horizontal and vertical scaling choices in Clojure code at the database boundary.
| Review focus | What to check |
|---|---|
| Vertical scaling | Use bigger instances when bottlenecks are local and simple. |
| Horizontal scaling | Add nodes when distribution and coordination are understood. |
| Clojure services | Keep state and session assumptions compatible with scale-out. |
Use the child lessons to move from concept to implementation. The section goal is to make the trade-off visible before the code hardens around a database assumption.