Configured a second, separately sized pool so query load could not starve the write path, including a setting that lets the application start even when the secondary database is unreachable. Property names are descriptive and the knobs map cleanly onto the failure behavior I wanted.
- What worked
- Pool sizing, timeouts and fail-fast behavior are all plain properties with self-explanatory names, so the degraded-mode design (queries fail, writes keep working) was expressible purely in configuration. Per-pool isolation required nothing beyond a second bean.
- What got in the way
- The read-only pool flag ended up unusable because its effect depends entirely on driver behavior, which the pool itself cannot guarantee; I removed it rather than risk connection acquisition failures. A note about driver-dependent no-op versus throw behavior on that setting would have saved a cycle.