Important step with cloud adoption is to manage quick cycles of learning and improvement of the cloud environment. The following presentation brought you by Amazon AWS guys contains great amount of slides including best practices and examples for Continuous Deployment, Optimization and Integration.
OpenX Source is a free, open-source ad server that allows publishers to manage their ad inventory and set up complex campaigns with sophisticated targeting rules.
Unfortunately, since OpenX has been focusing on their SaaS solution, the open source version is not well supported anymore. Nevertheless, many publishers still use and maintain their OpenX installations as there is a lack of open source alternatives offering the same flexibility and functionality.
Existing documentation to a great extent assumes a single server installation. For high traffic web sites delivering a large volume of advertisement impressions, there is a need for a more scalable setup.
In this article we will describe the steps we have taken to implement OpenX on a multi-server, auto-scaling setup running in AWS cloud and managed via Scalr. A similar approach could, of course, be configured outside the Scalr or even AWS context. We will mention some of the alternatives.
Newvem continuously monitors servers’ CPU load and notifies on high CPU loads. We consider an average CPU load of 80% and above as a high load. As high CPU load can lead to a major service availability risks, which results in service degradation. In order to protect the system one should consider changing the instance size or implementing a different scaling method. We suggest that you either:
The practice of shaping demand to fit the available resources can be found for example in transportation businesses, where airlines charges more for their service when demand is high and charge less to encourage more demand. In the real-time and interactive on-line world, the challenge is to ensure that capacity meets demand.
