Refactor db selection in SidekiqServerMiddleware
This change separates decision making from acting when considering how the database should be accessed in Sidekiq workers (primary vs replica nodes). This makes for a cleaner split between state decisions and side effects we need to perform based on them. This also fixes a problem we introduced earlier where the data_consistency job field was injected twice, and renames database_chose to load_balancing_strategy. Changelog: changed
Showing
Please register or sign in to comment