Online advertisers are concerned with Internet Advertising Bureau (IAB) categorizations. These categorizations represents themes or topics and can apply broadly to websites advertisements or other web data objects.

I developed and deployed a REST-full micro-service using Flask to train and update classifiers learning from web-data and to classify any document into a normalized vector representing the theme breakdown of the document into IAB categories. This service used Flask as the REST service layer, the multiprocessing module for process control, MALLET software (http://mallet.cs.umass.edu/) for classification, beautiful soup for data pre-processing, and Nutch/SOLR for crawling and indexing web data.

Determining the next ad-producer to solicit for a particular ad impression is not trivial. A good algorithm will take many factors into account, the two most immediately noticeable factors are revenue for the publisher (website hosting the advertisement) and the time to fill the ad slot.

In my work I've developed a suite of algorithms for solving this problem under different assumptions. A version of this work deployed in production use data aggregation over terabytes of log data to build distributions representing how much time a solicitation will take. The deployment used Flask as a RESTful microservice layer, Python, and SciPy for the main algorithms. More advanced research solutions make use of real time dynamic programming to achieve solutions with bounded suboptimality.

As part of SDN research work I developed a basic Software Defined Networking (SDN) solution based on Python, Berkley Sockets, and python remote objects (https://pythonhosted.org/Pyro4/). The SDN is built over TCP/IP and allows dynamically reconfigurable networking paths. In fact, in the paper on this topic the reconfiguration is done based on period flow estimates to ensure that devices are given uncongested networking paths. To our knowledge we are the first group to build an SDN over the remote object paradigm. With this approach, the client requests a connection rather than an address from the gateway. The connection returned is actually a remote object now shared by both the client and the network used for reads and writes by the client and reconfigured by the network administration as network conditions change.