The Bizo platform is constructed on the Amazon Web Services (AWS) suite of elastic IT cloud infrastructure services. As a recognized leader by AWS Bizo operates an auto sensing and auto scaling architecture which dynamically adjusts in real-time to increasing and decreasing demands for Bizo services. If you are not familiar with AWS here is an interesting article in the New York Times highlighting, among other things, the Netflix decision to move to AWS.
Key Points:
Key Points:
- 6 data centers in 4 geographic regions
- Geo load balancing and fail-over
- Operating at 99.99% up-time
- API average response time is 150 milliseconds as measured by Pingdom
- Data collector average response time is 90 milliseconds
As a real world example, Bizo technology was recently put to the test during the May 6, 2010 Market Crash -- check out the case study below:
May 6, 2010 Market Crash On May 6, 2010 the Dow dropped almost 1000 points during mid day trading. This "Crash" caused investors to flock to many Bizo publisher web sites seeking to learn about what was happening. This activity caused a 2.5x increase in requests for Bizo services to over 1500 requests per second. Bizo's auto scaling cloud architecture sensed the increase in requests and dynamically increased the required capacity to maintain response times. In fact response times (as measured by Pingdom) dropped from 150 milliseconds just before the spike to 100 milliseconds during and immediately after the spike. All of this happened automatically with no human intervention. Bizo customers and parters experienced no interruption in Bizo services from this massive increase in traffic. |  |
Requests for Bizo services increase by 2.5x
Bizo auto scales to meet demand
Bizo auto scales to meet demand
Response time lowers during spike
