As we continue to build (internal) useful operational modules for Prebid Server, we find that the configuration options are not ideal. Right now we have these two options:
Deploy host-level config
Update the dynamic (DB-based) account-level config in many accounts
We plan to build an another option to support cross-account dynamic use cases:
Dynamic (DB-based) module-level config.
Proposal
Establish a new configurable query similar to what exists for accounts. e.g.
settings.database.module-query: select module_code, config from module_config where status=”active”
Where:
module_code matches the module name
config is a JSON blob
A thread in PBS runs the module query periodically and stores the results internally. Make the assumption that data size will be monitored outside of PBS.
JSON merge the module’s DB config results with any account-specific config for the module. Account config would have priority over module config.
The Module interface to config doesn’t change – it sees the data in the module table as account config.
As we continue to build (internal) useful operational modules for Prebid Server, we find that the configuration options are not ideal. Right now we have these two options:
We plan to build an another option to support cross-account dynamic use cases:
Proposal
Where:
module_code
matches the module nameconfig
is a JSON blobA thread in PBS runs the module query periodically and stores the results internally. Make the assumption that data size will be monitored outside of PBS.
JSON merge the module’s DB config results with any account-specific config for the module. Account config would have priority over module config.
The Module interface to config doesn’t change – it sees the data in the module table as account config.