-
Notifications
You must be signed in to change notification settings - Fork 749
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Modular Architecture for Prebid Server #1734
Comments
Thanks to the community for a thorough review of the document through 3 meetings. All the feedback has been incorporated and it's certainly a better proposal for the time you all spent. Thanks. The draft notice has been removed. I'm going to open a separate issue to track some suggested improvements in logging. |
Update: this project is underway |
Core functionality implemented in PBS-G0 0.238.0. OpenRTB Blocking Module implemented in PBS-Go 0.239.0. |
Prebid Server (PBS) started as a simple server that just obtained header bids from a list of other server endpoints and forwarded the results back to the client.
Through the years, feature functionality has grown: currency conversion, events, privacy support, targeting options, first party data, etc. PBS host companies can turn off these features from server config, but they still bear the cost of additional server resources to host the unused features.
There's a long-term vision that PBS becomes the center of an ecosystem similar to what Prebid.js has become: many optional modules, perhaps even overlapping or mutually exclusive such as geo-lookup vendors or multiple brand protection modules.
As the server gets more and bigger features, it may not make sense for all companies hosting PBS to bear the cost and complexity of hosting and configuring all features.
To summarize, the high level goal of the project is to encourage a larger ecosystem of Prebid Server optional functionality without unduly burdening host companies. The most important component of this goal is a useful, consistent, and well-documented set of interfaces for extending server functionality. Some existing functionality may eventually be pulled out into modules (e.g. geo-lookups), but that refactoring will take time.
It is not intended that every future feature must be a module. There will be small features embedded directly in PBS-core, and perhaps even large complex features (e.g. Programmatic Guaranteed) that might not work well as a series of modules.
See https://docs.google.com/document/d/1QgQbIL06dsQQw-Qmw_JClXNsbjDmYQ09gU7iu6iox_M/edit# for the in-progress requirements document.
The text was updated successfully, but these errors were encountered: