Roadmap - datacratic/rtbkit GitHub Wiki

RTBkit is an open-source software framework designed to make it easy to create real-time ad bidding systems. It is a real-time bidder framework designed for use on advertising exchanges such as the Rubicon Project, Nexage, AppNexus, The Google Ad Exchange and others. On February 19th 2013, Datacratic released RTBKit as a technology preview release. The primary intent was to allow its evaluation by partners such as ad exchanges, SSPs and data providers.

RTBKit is software that is used by production systems at Datacratic and we are very committed that feature-specification should be informed by production and end-user experience as well as engineering considerations around high-availability, reliability and performance guarantees. The following document presents the roadmap for the coming year.

As a user if there are any issues that you would like to see addressed that are not on the roadmap please do not hesitate to let us know via the mailing list.

Please refer to the Architecture document for a detailed description of the components mentioned in this page.

2014 Priorities

UTF-8 Support (In Progress - Q1 2014)

The goal is to support internationalization throughout the RTBKit stack

Unified Configuration (In Progress Q1 2014)

Currently many parameters are either hard-coded or located in the boostrap.json file. The goal is to group all configurable parameters in one central location

Protocol versioning between agents and routers

Currently, whenever the protocol changes between the router and agents both the core stack and the agents need to be restarted. The goal here is for components to be be compatible across versions. For instance, agents running with an earlier version of the protocol would continue to function even if the core router is updated to a new version.

Focus on scalability

The goal is for RTBKit to support thousands of agents and a QPS volume that is in the order of hundreds of thousands. Currently some components are an obstacle to that goal either because they are singleton processes (i.e the Post Auction Loop) or because they have performance limitations(Graphite, ZooKeeper). These scalability bottlenecks will be addressed.

Exchange Connectors

The goal is to increase the number exchanges that are supported by RTBKit. Based on the community survey high-demand connectors are OpenX, Pubmatic and Nexage. If you would like to help on building these or have any connectors that you would like to contribute please do get in touch - contributions are most welcome!

Performance benchmarking

The goal is to develop a set of tools that will allow the generation of performance benchmarks for RTBKit as a whole as well as individual components including third party components such as Graphite and Zookeeper. This will make it easy to measure the impact of changes on system performance.

Alternative build system and packaging

The goal is to explore alternative and more standard methods for building and packaging for RTBKit.